Re: module-nohide

Dan,

Dan <[email protected]> writes:

> I often find myself switching between debugging and release
> environments. When debugging, the symbol hiding of the (module) macro
> gets in the way. It's annoying to keep adding functions to the export
> list and then remove them.
>
> A better solution would be a module-nohide macro that ignores its
> export list. Then I could just tag "-nohide" to modules when I feel
> like debugging. Is there an easy way to write this macro, or a better
> solution to my problem?

It is impossible to get a module to export all its bindings; exports
always have to be listed explicitly somewhere.

One thing you could do is use interfaces:

  (define-interface my-module-exports
     (id ...))
  
  (define-interface my-module-additional-exports
     (id ...))
  
  (define-compound-interface my-module-debug-exports
     (my-module-exports my-module-additional-exports))
  
  (define-module my-module <exports>
     defn ...)

Replacing <export> with either 'my-module-exports' or
'my-module-debug-exports' then allows you to switch between the ordinary
and debug version of a module. You still have to list the exports in the
interface definitions but at least the switching is easy.


Matthias.

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642