Master Reference (The Deep Dive)

This page provides a technical breakdown of every field, variable, and command logic in the BigC ecosystem.


🌐 BigWeb (Server Context)

Every time a request hits the server, BigWeb populates these System Variables for your logic to use:

FieldTypeDescription
RequestPathStringThe full URL (e.g., /view?page=syntax).
RequestMethodStringEither GET or POST.
RequestBodyStringThe raw data sent in a POST request.
Sbig_Response_BodyInternalSet via reply with. Holds the text to send back.
Sbig_Response_FileInternalSet via reply file. The path to the file to serve.

📡 BigNet (Networking)

BigNet manages the state of your connection. These commands modify the Global Client State:


🏠 HBig (Toddler's HTML)

HBig maps simple words directly to HTML5 tags.

BigC WordHTML ResultNotes
box class "x"<div class="x">Use end box to close with </div>.
header "x"<h1>x</h1>Used for page titles.
text "x"<p>x</p>Standard content blocks.
button "x"<button>x</button>UI action triggers.
input "x"<input placeholder="x">User data capture.
link "x" url "y"<a href="y">x</a>Navigation.

🎨 BCss (Toddler's CSS)

BCss automatically handles unit conversion and shortcuts.


🧠 BigC Core (The Interpreter)

The internal Rust engine (Interpreter struct) tracks three critical fields:

  1. variables: A flat map where every value is a String. Numbers are parsed only when math is performed.
  2. last_condition_met: A simple true/false flag. Every if updates this. or only runs if this is false.
  3. loop_stack: A list of active loops. Each loop tracks its start_index and count (for the nonstuck safety break).

🔒 The Vault (Data Structures)