Re: [Chicken-users] Modules and environments

[Thomas Chust]

2009/8/30 Peter Bex <address@hidden>:
> [...]
> I disagree. If this should print #t you should also be able to obtain
> a reference to the macro using (eval 'hello (interaction-environment)),
> but that's not possible since macros are not first-class.
> [...]

Hello,

that's beside the point: Macros just like modules are syntactic
features of the language. Therefore I think it is quite logical that
macro identifiers and identifiers possibly mangled by the module
system behave similarly in some respects.

Futhermore, environments are an implementation detail of the runtime
system. It is, as I said, maybe not very intuitive if the internal
implementation does not use the same names for variables as your
source code, but it's not a bug. Following your logic one could also
claim that it is a bug that after dlopening a chicken-compiled shared
library from C you cannot access the Scheme bindings under their
Scheme names using dlsym. I think that such behaviour is perfectly
fine.

cu,
Thomas


-- 
All these theories, diverse as they are, have two things in common: They
explain the observed facts, and they are completely and utterly wrong.
                               -- Terry Pratchett, "The Light Fantastic"