Hi Kashyap,

> I think I have fully digested gen3m.c at this point :). I am now trying to
> figure out how to do FFI min miniPicoLisp and I realized that only pil64
> has native/lisp support. Is there any reason it could not be done in the
> 'c' implementation of pil32?

Pil32 and miniPicoLisp are written in C, and C does not support calling other
functions in a generic way. This is one of the reasons pil64 was written in
assembly (in addition to stack control and CPU status bits).


> I just wanted to make sure that there is no
> "impossibility" about attempting to port the native/lisp functions to
> miniPicoLisp.

Meanwhile there *is* a way: libffi - which takes care of that low level stuff. I
use it now in pil21 (only a proof of concept so far, I hope it is indeed
portable enough).


> A quick question on gen3m.c - I noticed an unused parameter '*mem' in mkSym
> - is there a reason to let it remain?

Right, it seems to be replaced in the function by always "(Rom+%d)", so it is
indeed not needed.

☺/ A!ex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to