Project Context and Principles

cREXX is shaped by three overlapping contexts:

• REXX as a language with a strong tradition of readability and practical automation
• modern implementation work around compilers, bytecode, tools, and portable runtimes
• the desire to keep the language extensible without turning it into something unrecognisable

Why A New Implementation

The project explores what REXX can become when implemented from the ground up with a modern toolchain and explicit intermediate forms. That gives the project room to improve portability, packaging, host integration, and implementation clarity while still respecting the language's original human-centred design.

Direction Of Travel

cREXX development is expected to keep moving in these directions:

• a stronger as-built release documentation set
• a practical Level B foundation for libraries and tools
• a clearer path for classic REXX compatibility work
• a richer hosted and embedded integration story
• more library functionality implemented in REXX itself
• eventual self-hosting where that genuinely simplifies the system

Documentation Boundary

This page describes direction. It intentionally avoids current syntax, instruction formats, build commands, and API contracts. Those details belong in the release documentation and source tree.