Hi folks,
Here's a small patch that puts `module-environment' into the eval
module. I propose this as an alternative to making `eval/meta` a public
API, which it feels like we were mostly doing just to make
"chicken.eval" export more than one thing. I think putting
`module-environment' there
This syntax-only library contains CHICKEN's "module language" and
currently contains: module, import[-*], export and reexport.
TODOs have been left in place to remind us to move `functor` and
`define-interface` into this module, as well.
---
chicken-syntax.scm | 2 +
expand.scm
Hi all,
Here's a patch that adds a "chicken.module" module according to some of
the discussion in the "Add unexport form to modules" thread, and from
the "undecided" section of c-l-r (which already proposed a lot of the
same changes, in fact).
The library is syntax-only and contains CHICKEN's
As of afd7867, we can make these values available to the other files
that need to use them without making them part of the chicken.export
module's public API by assigning directly to namespaced identifiers.
---
core.scm | 4 ++--
expand.scm | 17 +
2 files changed, 11
Hi all,
As Kooda found out when working on #1379, there's still some problems
with the symbol GC stuff in CHICKEN 5. Sometimes you'll see an assertion
failure in update_symbol_tables: assert(!C_persistable_symbol(sym)) will
bail out due to some symbols being released while they still had a
