Re: [Chicken-hackers] [PATCH] Moving some things from library.scm and eval.scm to internal.scm

[felix . winkelmann]

> I think we should strive to make library the first, and potentially the
> only, unit that the user needs to care about when distributing compiled
> C or compiling programs with "-explicit-use". These changes move things
> further away from that ideal by making programs that use the `time`
> macro (and probably `syntax-rules`, though I haven't looked at that
> quite as closely) depend not just on library but also on internal, and
> without adding anything to make sure the internal unit will actually be
> loaded as necessary. An example program that will no longer work is the
> following:
>
>     ;; compile with `csc -x example.scm`
>     (import chicken)
>     (time (print 1))
>
> Even without the "-x", it's only due to the fact that the eval unit is
> loaded by default that this program runs at all, since that unit depends
> on internal.

+1

It is extremely handy to be able to ship just a few C files for distributing
a file. I used this approach for some language implementations built on
top of the CHICKEN runtime.


felix