Frequently Asked Questions
Is Nebo ready for production use?
Section titled “Is Nebo ready for production use?”This website does not certify production readiness or current compiler stability. Nebo remains in development. Read the limitations before relying on a feature or environment.
Can I try a program now?
Section titled “Can I try a program now?”You can study the exact hello example and its recorded commands. Its successful run belongs to one local neboc 1.0.1 binary. A current SDK installation is not verified here.
Why does the homepage show 1.0.0 when 1.1.0 exists?
Section titled “Why does the homepage show 1.0.0 when 1.1.0 exists?”The homepage preserves a historical release reference. The hello test uses a separate 1.0.1 compiler, and GitHub also provides a public 1.1.0 release. Downloads keeps these records distinct.
Does “Planned” mean the compiler implements a feature?
Section titled “Does “Planned” mean the compiler implements a feature?”No. The homepage uses it as a legend for future validation work. It does not assign maturity to an implemented capability.
Why did my program print nothing in the terminal?
Section titled “Why did my program print nothing in the terminal?”The recorded hello used a native Console window. Terminal output, retained test traces and visible desktop presentation are different observations. See Console and I/O.
Where can I report a bug or follow development?
Section titled “Where can I report a bug or follow development?”Use the public repository and issue tracker. Include a minimal example, exact version and diagnostic. Avoid posting credentials or private data. About identifies the project and contact route.
Does this website execute Nebo code?
Section titled “Does this website execute Nebo code?”No. Examples are static documentation. Search runs in the browser over the site’s index; there is no online compiler or account system.