Skip to main content
Version: 0.0.2

RayQuiro 0.0.2

RayQuiro 0.0.2 is the current Windows-first RayQuiro release. It is built around the rqio CLI, direct .rq execution, VM packaging, native module installation, and a broader engine/runtime surface than 0.0.1.

What Changed In 0.0.2​

The most important structural change is the split between:

  • the core language and runtime
  • built-in system modules
  • official installable native modules

That means 0.0.2 no longer treats every higher-level feature as if it were always bundled into the core language surface.

Core Language And Runtime​

RayQuiro 0.0.2 includes:

  • .rq source files
  • direct execution through rqio
  • a VM path for supported scripts
  • native build through rqio build
  • bytecode packaging through .rqb
  • bundle output for closed distribution

The core language includes:

  • variables with var and let
  • functions with fn
  • conditions and loops
  • arrays and indexing
  • multiline strings with """ ... """
  • a growing built-in utility layer

Built-In System Modules​

These namespaces are part of RayQuiro itself and do not need separate installation:

  • rayquiro.fs
  • rayquiro.env
  • rayquiro.process
  • rayquiro.time
  • rayquiro.json

Use them for:

  • file and directory work
  • environment variables
  • process execution
  • time helpers
  • JSON parsing and serialization

Official Installable Native Modules​

In 0.0.2, these are official installable native modules distributed separately from the core runtime:

  • rayquiro.web
  • rayquiro.ui
  • rayquiro.app
  • rayquiro.engine

Install them with:

rqio install rayquiro.web
rqio install rayquiro.ui
rqio install rayquiro.app
rqio install rayquiro.engine

Install into the current project instead of globally:

rqio install rayquiro.engine --local

Execution And Packaging Modes​

rqio file.rq​

The normal runtime path.

Use it for:

  • direct script execution
  • system module workflows
  • source frameworks
  • installed native modules

rqio run --vm file.rq​

The VM path.

Use it for:

  • supported core scripts
  • .rqb workflows
  • more closed distribution flows

rqio pack file.rq​

Creates a .rqb bytecode package.

rqio bundle file.rq -o build/my-app​

Creates a distributable bundle directory.

rqio build-vm file.rq -o build/my-app​

VM-focused bundle alias.

rqio build file.rq​

Creates a Windows executable.

In 0.0.2, normal build flow does not treat generated C++ output as a user-facing artifact.

Project Layout​

A typical RayQuiro project uses:

  • rqproject.json
  • main.rq
  • .rq_modules/
  • build/

Minimal starter flow:

rqio init my-app
cd my-app
rqio

Example rqproject.json:

{
  "name": "my-app",
  "version": "0.0.2",
  "entry": "main.rq",
  "build_dir": "build"
}

Recommended order:

  1. Installation and CLI
  2. First Program
  3. Syntax Basics
  4. Imports and Modules
  5. System Modules
  6. official module pages
  7. Release 0.0.2