>>122
Trying to use compile-time constructs to reflect changes at runtime is considered a smart thing to do in
Scheme?
When I write my macros (albeit I'm a CLer, but not like Scheme macros don't have the fundamental concepts of compile and runtime) I always have a very clear view of what is ran and when (be it read-time, compile-time, load-time, run-time, etc). It's a grave mistake to think something which is ran in a latter time (such as a runtime) to be able to affect something which occurs before it(such as compile or read time).