Orkuncakilkaya
aca263642d
Getting started meant cloning the repository, bootstrapping a compiler and
learning a task runner called `x`. That is a contributor's workflow handed to
everyone who wants to try the language.
Installing is now one command:
curl -fsSL https://workshopsoft.pages.workshopsoft.io/ludic/install.sh | sh
install.sh puts a complete toolchain — compiler, CLI, engine runtime, bundled
ludic.* packages, formatter, language server — in ~/.ludic and adds it to PATH.
Prebuilt artifacts are checksum-verified; where a platform has none, or the
release predates this layout, it bootstraps from the compiler's own IR seed with
clang. The docs site publishes the script beside the pages that quote it, so the
page and the script can never come from different releases.
`x` becomes `ludic`, and the surface splits by audience. A user of the language
sees `new`, `run`, `build`, `test`, `add`, `fmt`, `lsp`, `doctor`, `upgrade`;
`ludic new` scaffolds a project that builds and plays as it stands. Everything
the toolchain repo needs moved under `ludic dev` — build, test, reseed,
bootstrap-cfree, docs-gen, release — unchanged apart from the namespace. Those
tasks read arguments one position further along, so dispatch_dev sets a shift
and commands use arg_n()/arg_total() rather than each knowing its own depth.
Release artifacts become complete install roots (bin/ beside runtime/, packages/
and VERSION) rather than bare binaries, which is what the installer unpacks.
`ludic dev test` asserts the whole shape: it stages an install, puts it on PATH
with no LUDIC_HOME, and runs new -> build -> test through it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
48 lines
1.5 KiB
Text
48 lines
1.5 KiB
Text
# scenes — one active scene at a time, each grouping handlers into layers behind
|
|
# an implicit active-scene register (see LANGUAGE.md §"Scenes & layers").
|
|
#
|
|
# Running it (feed a few keystrokes so the loop ticks) prints:
|
|
# 1000 1 101 102 2 3 900 201 900 202 900
|
|
# 1000 Boot (a global handler) runs once at Start
|
|
# 1 Title is `start`; its `on enter` fires at boot
|
|
# 101 frame 1 Update: only Title.Main.Tick runs (Play is not active)
|
|
# 102 frame 2 Update: Tick reaches 2 -> `become Play`…
|
|
# 2 3 …which runs Title's `on exit` then Play's `on enter`
|
|
# 900 Play renders the same frame it is entered (Hud.Draw)
|
|
# 201 900 frame 3: Play.World.Step, then Hud.Draw
|
|
# 202 900 frame 4: Step reaches 2 -> quit(); Hud.Draw paints the last frame
|
|
#
|
|
# bin/ludic dev game-build bin/ludicc examples/lang/scenes.ludic /tmp/scenes
|
|
# printf 'aaaa' | /tmp/scenes
|
|
program SceneDemo {
|
|
var counter: int = 0
|
|
|
|
handler Boot phase Start { counter = 0; print(1000) }
|
|
|
|
scene Title start {
|
|
on enter { print(1) }
|
|
on exit { print(2) }
|
|
layer Main {
|
|
handler Tick phase Update {
|
|
counter += 1
|
|
print(100 + counter)
|
|
if counter >= 2 { become Play }
|
|
}
|
|
}
|
|
}
|
|
|
|
scene Play {
|
|
on enter { print(3); counter = 0 }
|
|
on exit { print(4) }
|
|
layer World {
|
|
handler Step phase Update {
|
|
counter += 1
|
|
print(200 + counter)
|
|
if counter >= 2 { quit() }
|
|
}
|
|
}
|
|
layer Hud {
|
|
handler Draw phase Render { print(900) }
|
|
}
|
|
}
|
|
}
|