lunaamora/4orth

4orth is a Porth compiler with WASM, WASI and WASM-4 targets

Hello, my name is Luna 👋

I'm a game design student and work with programming and game development.

My main technologies 🧡

4orth's Issues

Implement the return stack

Local memories in the current version are implemented as a hack, using wasm locals instead of a return stack. This causes problems when using the pointer to a local mem to do things other than direct read or write.

A proper return stack must be implemented to fix this issue and lay the ground work to #1

Cannot manually import procedures with inline WAT

Context

I am currently building a WASM layer for p5.js and, just for fun, I wanted to add Porth support. However, I am running into an issue with importing one of my functions. Since print is a Porth intrinsic, I could not import a procedure with the same name. So I resorted to this:

wasm
  "(import \"env\" \"print\" (func $print (param i32)))"
end
// -- 88 lines of "import proc <name> <signature> in end"
inline proc print-i32 int -- in
  wasm int -- in
    "(call $pop)"
    "(call $print)"
  end
end

However, I get an error from wasm2wat:

web/examples/colors.wat:127:2: error: imports must occur before all non-import definitions
(import "env" "print" (func $print (param i32))) ;; OP_INJECT_CODE 0
 ^^^^^^

I tried putting the (import "env" ...) before include "wasm-core.porth" and it still gives the same error (just different line numbers). Is there anything I can do or do I have to not include this procedure for now until you (maybe) fix it? (I already had to omit quite a few functions because of floats)

Add let-bindings support

Add support to the following Porth Ops:

• OP_BIND_LET
• OP_BIND_PEEK
• OP_PUSH_BIND
• OP_UNBIND