Quoth Sebastian Tennant <[EMAIL PROTECTED]>:
Hi all,

Many thanks to all responders, especially to Ludo' for answering my
question directly.

The macro definition I was searching for is simply this:

 (define-macro (definer var val) ;var must be a symbol
   `(module-define! (current-module) ,var ,val))

Wrapped within a 'for-each' this macro allows me to bind as many
variables as a like in a single stroke.

Why not use the module namespace as a top-level hash table Dale?  Isn't
that essentially what a module namespace is, or at least what it's for?

Is there a really good reason to avoid doing this?

Apart from non-portablility, what difference does it make whether a
variable is bound using 'define' or my 'definer' macro?

Thanks once again.

Sebastian





Reply via email to