RayPals/Claro
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: clarify Claro v1 status and validation

Browse Source
This commit is contained in:
Hermes Agent
2026-06-07 03:03:13 -06:00
parent 0da1095c03
commit 1e0ea06d21
74 changed files with 2351 additions and 336 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/LINTER.md
+4 -5
View File
@@ -2,16 +2,15 @@
`claro check file.claro` looks for beginner mistakes before running a program.
RC3 catches:
The current checker catches:
- unknown commands
- command typos such as `PRINT` or `PRNT`
- missing `TO` in `SET`
- missing `AS` in `ASK`, `GET`, and `COUNT`
- missing `ENDIF`, `DONE`, `LEARNED`, `ENDTRY`, and other block endings
- missing required words in older compatibility forms
- missing block endings such as `END`, `ENDIF`, `DONE`, `LEARNED`, and `ENDTRY`
- `ELSE` without an `IF`
- `CATCH` without a `TRY`
- common misspelled variables
- variables created by `ASK`, `GET`, `COUNT`, `READ`, `PARSE`, `MAKE`, `FOR`, and `FOR EACH`
The checker is meant to be friendly, not scary. It is still not a complete static analyzer.
The checker is meant to be friendly, not scary. It is still not a complete static analyzer; use `claro typecheck` for the stronger type-checking pass documented in `ADVANCED_STATIC_TYPING.md`.