luxferre/clyx
1
0
Fork 0
Code Actions Activity

readme upd

Browse Source
This commit is contained in:
Luxferre
2026-07-03 16:30:57 +03:00
parent 9e91771e76
commit 10f0b39d8e
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -5
View File
@@ -101,6 +101,11 @@ clyx.repl()
``` ```
To run a Clyx source file directly, issue `clyx.clyx('path/to/file.clx')` instead. To run a Clyx source file directly, issue `clyx.clyx('path/to/file.clx')` instead.
Caveats:
1. The entire operation is rather slow (which is expected for an interpreted runtime on top of CircuitPython on this class of machines) and may sometimes overflow the allocated (native) Python stack. As such, it's not recommended to `src` files from the REPL if you can run them directly instead.
2. Don't forget to mount an SD card or run `unlock_rootfs()` if you want to use file writing capabilities inside T-DeckARD environment.
### Running the Go implementation ### Running the Go implementation
To run the REPL, execute the compiled `clyx` binary without arguments: To run the REPL, execute the compiled `clyx` binary without arguments:
@@ -115,11 +120,6 @@ To run a program directly, pass the path to the `.clx` file as an argument:
./clyx path/to/program.clx ./clyx path/to/program.clx
``` ```
Caveats:
1. The entire operation is rather slow (which is expected for an interpreted runtime on top of CircuitPython on this class of machines) and may sometimes overflow the allocated (native) Python stack. As such, it's not recommended to `src` files from the REPL if you can run them directly instead.
2. Don't forget to mount an SD card or run `unlock_rootfs()` if you want to use file writing capabilities inside T-DeckARD environment.
## FAQ ## FAQ
### Where does the name Clyx originate from? ### Where does the name Clyx originate from?