Hi George!
I can attest that writing your own scheme interpreter is fun and
educational. I've had success trying out language design ideas with
interpreters. I implemented a very simple heap-based interpreter, and tried
out a similar idea to yours with no problem (but I was using environments as
I was thinking about writing my own scheme interpreter for the heck of it. It
might not make sense for some implementation strategies. What would be a good
implementation strategy for this technique.
-Original Message-
From: Thomas Chust
To: George Rogers
Cc: Chicken-users
Hi,
I'm trying to wrap some utility functions in a module into a .so. I'm
getting undefined symbol errors, and I'm not quite sure how to resolve
them:
$ csc -s lib.scm -j lib
Undefined symbols:
"_C_regex_toplevel", referenced from:
_f_1400 in lib.o
"_C_symbol_2dutils_toplevel", referen
2011/3/24 George Rogers :
> What do you think about using evaluation environments as a basis for a
> module system.
> [...]
Hello,
this may look like a good idea but I suspect it isn't very suitable
for CHICKEN, because CHICKEN's evaluation environments contain no
syntax information but only runt
_/_/_/ _/_/_/
_/_/_/_/ _/_/_/ _/ _/ _/_/_/_/_/
_/_/_/ _/ _/_/_/ _/_/_/_/ _/_/
_/_/_/ _/ _/_/ _/_/_/_/
_/_/_/ _/_/ _/_/_/_/ _/_/_/_/_/ _/_/
--[ I
