Compile and Run

Prerequisites and scope

Use the exact hello source and compiler identity to interpret this record. An arbitrary neboc on your PATH, even one reporting 1.0.1, is not necessarily the recorded binary. Installation of a current SDK remains unverified here.

Recorded workflow

The historical source check succeeded. The build and launch commands shown with the validated example are:

neboc build hello.no -o hello
./hello

Run a reproduction only in a working directory you own, with no existing hello output that you need to preserve. The first command requests an executable named hello; the second launches it. These are recorded commands, not a claim that the current public SDK passes them.

What success looked like

A native Console window displayed Hello from Nebo!. Closing it through the window manager exited cleanly. Terminal silence alone is therefore not evidence that the program failed. Conversely, a successful build alone does not demonstrate visible output or correct runtime behavior.

If your result differs

Record the compiler digest and version, source file, command, exit status, diagnostics and display environment. Check Console and I/O and limitations. Do not work around a failure by silently changing the source and presenting the result as this test.

For reports, use the project issue tracker with a minimal reproduction and no private files or credentials.