[Chicken-users] eggs exporting syntax and functions

[Dan]

Hi, I'm trying to create an egg that exports both
procedures and macros. The egg creation docs seem to
suggest the follolwing (cumbersome) solution:

* the main extension, main.scm contains just macros
* in install-extension, mark the extension as (syntax)
* package the procedures in defs.scm
* in install-extension, add (require-at-runtime defs)

There's also the option of wrapping the main Scheme
file in a module, then forcing users of the egg to
(import) that module. But that seems dubious --
suppose that the main file is myegg.scm, which
contains

(module myegg (mac proc) ...)

I compile myegg.scm to produce myegg.so. Both the scm
and the "so" version are installed in the egg repo.
Then as a user I type

(require-extension myegg)
(import myegg)

Does proc now refer to the "interpreted" version in
myegg.scm, or to the compiled version in myegg.so?

-- Dan


 
____________________________________________________________________________________
Everyone is raving about the all-new Yahoo! Mail 
(http://advision.webevents.yahoo.com/mailbeta/)