Chuigda WhiteGive
Chuigda WhiteGive
Named after the SABRE engine, this will be our AOT target. We'll use [emei](https://github.com/imlyzh/emei) for code generation.
As mentioned in #5, an instruction pretty printer is indeed necessary. Some work have been done [here](https://github.com/Pr47/Pr47/blob/7d4f51f10a74b7437b26b7b174b9243e028ae1b8/pr47-core/src/vm/al31f/insc.rs#L479). This is low-hanging fruit.
The current "API"s of FFI functions heavily relies on Rust traits. maybe some raw APIs will be useful when implementing foreign language implemented engines (`AL31FU`, for example) or JIT engines.
According to our investigation, c0i seems to be a good platform for us to test the functionalities of AL31FM2. The basic infrastructure and several testings have been set up in...
Named after a [Russian jet engine](https://en.wikipedia.org/wiki/Saturn_AL-31), the AL31F will be the default, bytecode interpreting engine for Pr47. This is the tracking issue of the engine implementation. ------ Task list (non-exhaustive):...
# Lexer - [x] identifier - [x] keyword - [ ] symbol - [x] comments - [x] literal - [x] numeric - [x] string - [ ] kharakter # Parser...
Currently we don't have any documentation about the VM design, but obviously there's a design in the developer's mind. It is of lot value for us to write some documentation...
Consider the following Rust function： ```rust fn foo(x: &mut S, y: &mut S) { /* ... */ } ``` This function may be registered into Pr47 program, and then called...