David A. Wheeler scripsit: > ; Set up what we must at the topmost layer, and then define and invoke: > ; (readable-kernel-module-contents (exports ...) body ...) > ; - a macro that should package the given body as a module, or whatever your > ; scheme calls it (chicken eggs?),
Dude, you have a hold of the Tar Baby here. R6RS and R7RS libraries can't be the result of a macro, neither as a whole nor in part. All you've done is trade off one set of portability breakers for another. I recommend you do what Schemers have done from time immemorial: just write straight code, using a convention like prefixed "%" for internal-only functions and macros. That way you can load it in any Scheme (within reason) and watch it work. Adapting it to X Scheme's notion of a module should be left to X Scheme experts. This is what I've been doing with my SRFI implementations: plain code, plus a shim file to add stuff from R7RS-small that I need, plus modules for Chicken (R5RS-plus) and Chibi (R7RS), both of which fortunately support "include". Yes, it's more complex to use than one all-singing-all-dancing file. But it's much easier to port, even if it does less of the work for you. -- Long-short-short, long-short-short / Dactyls in dimeter, John Cowan Verse form with choriambs / (Masculine rhyme): co...@ccil.org One sentence (two stanzas) / Hexasyllabically Challenges poets who / Don't have the time. --robison who's at texas dot net ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
