V12.0 BASE CONTRACT

First program

First verify the frozen release fixture, then create and run a DByte file that belongs to you.

DByte 12.0 · Getting started

01 exact release hello§

RUNNABLE · WINDOWS X64 · EXACT RELEASE FIXTURE

print("Hello, DByte!")

Source identity: examples/hello.dby in dbyte-v12.0.0-windows-x64.zip.

02 verify the shipped file§

COMMAND · WINDOWS POWERSHELL · HOSTED TREE + VM

dbyte check examples\hello.dby
dbyte run examples\hello.dby
dbyte run --vm examples\hello.dby

EXPECTED PROGRAM OUTPUT

Hello, DByte!

SUCCESS GATE: dbyte check returns without a diagnostic and both hosted engines print the same exact line. A single hello run is a smoke test, not proof of the whole compiler.

IF CHECK · RUN · VM FAILS → READ DIAGNOSTICS

03 create your own program§

RUNNABLE · WINDOWS POWERSHELL · USER-CREATED FILE

Start from any working directory where you are allowed to create files. This example creates a new folder and writes the complete source without requiring an editor.

New-Item -ItemType Directory -Force .\hello-demo | Out-Null
Set-Location .\hello-demo
@'
print("Hello from my file!")
'@ | Set-Content -Encoding ascii .\hello.dby
Get-Content .\hello.dby

WORKING TREE

hello-demo\
`-- hello.dby

COMMAND · WINDOWS POWERSHELL · HOSTED

dbyte check .\hello.dby
dbyte run .\hello.dby
dbyte run --vm .\hello.dby

EXPECTED OUTPUT FROM EACH RUN

Hello from my file!

SUCCESS GATE: the file shown by Get-Content is the file you created, dbyte check emits no diagnostic, and tree/VM output agrees exactly.

If dbyte is not on PATH yet, finish Install troubleshooting. For parser/type/runtime failures, read Diagnostics.

CONTINUE: BUILD · RUN · TEST — HOSTED WORKFLOW for a second self-created file with explicit check, tree and VM gates.

04 second example — function syntax§

ILLUSTRATIVE SITE/SOURCE EXAMPLE · NOT THE RELEASE HELLO FIXTURE

fn square(value: int) -> int:
    return value * value

print("ONE LANGUAGE")
print(square(7))

This example demonstrates function syntax after the exact release hello and after the user-created-file workflow. It is deliberately not presented as the canonical first program.

05 mechanics · boundary§

Hosted source enters the shared AST and canonical semantic analysis before the tree or VM execution path. Backend divergence is a parity failure; neither engine is allowed to reinterpret the source.

06 next step§

BUILD · RUN · TEST → BASICS → ZERO TO USEFUL → LANGUAGE TOUR

SOURCE POLICY: the release hello is exact v12.0.0 evidence. The user-created hello is a runnable onboarding example. The function example is explicitly illustrative.