On 9/25/05, felix winkelmann <[EMAIL PROTECTED]> wrote: > I recommend running spiffy exclusively in csi, since you need > an interpreter with all non-standard macros anyway. > Alternatively, do an > > (eval '(require-extension chicken-more-macros)) > > at runtime to have non-standard syntax available (but > the macro-expanders are interpreted, then. Also needs a newer > chicken). > To have a fully compiled, custom interpreter with non-standard > syntax, put > > (declare (run-time-macros)) > (include "chicken-more-macros")
This seems to work, thanks. What are the disadvantages of doing it this way as opposed to running it in csi? _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
