Re: custom module loading and compilation

I wrote: > This works when I run Guile with --no-auto-compile, but with > compilation enabled, I get: > ;;; Unbound variable: my-load > How can I make the binding visible to the compiler? In case anyone else runs into this: I solved it by wrapping the definition of my-load in (eval-when (expand ev

custom module loading and compilation

Hi. I'm writing a custom module system that avoids the standard search path and list-of-symbols naming scheme. Instead of using use-modules and define-module, I have a roughly similar procedure, let's call it my-load, that creates a module with make-module and loads a file into it with primitive-

Re: defining macros within eval

Maxime Devos wrote: > For an example in the wild, see > e.g. > . Thanks (to Jean as well) for all the suggestions. Can you point me to an example of where include/sexp is used? To take a step back, my ultimate goal

Re: [PATCH] Improved string writing

Kevin Ryde <[EMAIL PROTECTED]> wrote: > Alas I think that'd be an incompatible change, programs printing a > prompt or progress info probably depend on immediate output as the > default. But the output can be immediate without splitting it up into multiple system calls. (display "foo") can result