On 09/10/2009 03:16 PM, Brian Harvey wrote:
>> When a procedure is redefined, existing calls may or may not be affected;
>> (Anybody have problems with these?)
>
> Yes! If I redefine a procedure (including, btw, primitives) I want the new
> version to apply everywhere, including already-loaded code. This is a
> requirement for interactive debugging.
It's a requirement for one style of interactive debugging.
It may not be practical if you have a compiler that does
compile-time name binding or inlining or type-checking, for example.
> (I think I understand why you're saying no for macros, but it makes me sad.
> It's not very jewel-like to have different redefinition rules for different
> kinds of things. It makes the language that much harder to learn.)
It is possible for a REPL-like environment to keep track of
"dependencies", so if you re-load one of more definitions
then any other definitions that made use of the changed
definitions is automatically re-compiled/re-loaded.
But that has its own sets of problems and anomalies.
--
--Per Bothner
[email protected] http://per.bothner.com/
_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
