Overview
PriyoScript stable handbook, from setup to advanced patterns.
PriyoScript is a human-first interpreted language with readable keywords, bytecode VM execution, first-class arrays, modules, OOP, and structured diagnostics.
Stable Scope
This handbook documents stable features only. Canary docs may include incomplete or changing behavior.
History of PriyoScript
PriyoScript started as a language-learning and language-design project with one central idea: programming should feel readable for humans first, then optimized for machines.
Over time it evolved into a full language pipeline:
- Lexer (reads characters and makes tokens)
- Parser (builds syntax structure)
- Compiler (turns syntax into bytecode)
- VM (executes bytecode step by step)
Why PriyoScript was made
- Reduce fear for beginners
- Keep errors understandable
- Keep syntax expressive but strict
- Help learners transition from JavaScript/Python/C/Java
How program execution works (very simple)
Imagine a teacher reading your homework:
- Read each word (
lexer) - Check sentence grammar (
parser) - Convert it to machine instructions (
compiler) - Execute instructions (
VM)
If grammar is wrong, you get syntax error. If logic breaks during execution, you get runtime error.
Who this handbook is for
- New users who want to write and run
.priyoprograms - Learners moving from JavaScript/Python/C/Java concepts
- Contributors who need precise language semantics
Learning path (base to advanced)
- Installation
- Quick Start
- Changelog
- Syntax Basics
- Control Flow
- Functions
- Classes & OOP
- Arrays
- Modules and Packages
- Error Handling
- CLI
- REPL
- Error Codes Reference
First runnable program
monalisa {
priyoTell("Hello, PriyoScript!")
}monalisa hello.priyoCurrent limitations
Ecosystem maturity
PriyoScript core language features are stable, but ecosystem tooling and third-party package availability are still growing.
Compatibility scope
PriyoScript is its own language/runtime, so it does not directly execute JavaScript/Python libraries without adapters.
Contributors are welcome
You can contribute by improving docs, examples, tests, diagnostics, and runtime features.
Contributing
Share expected behavior, actual behavior, sample .priyo code, and environment details when
reporting issues.
Last updated on