Search Results for "size"

Project aims to implement a C-like language interpreter with small code and memory footprint for 32bit microcontrollers. At the time of writing, parser code size for Cortex-M3 is less than 10K and VM is less than 3K. RAM requirements mostly depend on code size and complexity, but few kilobytes should be enough to handle most reasonably simple cases. Parser and VM are written with code size priority, not security. Project should not be used to run code (and bytecode) from untrusted sources.

...not bytecode or any typical implementation for vm. in fact, it encodes functions and keywords for a smaller code, which is good for small devices and embebbed devices. small code, small size, RUN faster.

The project was originally created to run programs from a MicroSD card on an ATmega16 (without reprogramming it). SBI is a generic library (platform indipendent) that lets you run programs from a stream (es. File). The programs are a sort of bytecode, and they are interpretated at the moment. So you don't have the better speed, but for now this is the only way to run programs from RAM (or SD) on Harvard architectures.

"The Engine" is a game creation engine with built-in classic type BASIC interpreter (as known from old 8-bit computers), screen editor and full-screen editor, using OpenGL and SDL (currently POSIX only, but portable, in principle). It is aimed at game developers with little spare time, and tries to reduce program size with powerful commands that takes as much coding effort off the shoulders of the developer as humanly possible. The BASIC interpreter supports only labels, not line numbers, and the program is written with the built-in editor. Interpreter and graphics engine run in parallel, in separate threads, and hence interpreter speed is not an issue. ...