I'm responding as a user/implementor, not speaking for the editors.
For what it's worth, I prefer that an implementation be allowed to do any
of the following for each violation it detects:
* reject the program prior to execution,
* issue a warning prior to execution and either abort or raise an
exception at run time, or
* raise an exception at run time.
To be clear, in cases where an implementation is required to raise an
exception with condition &violation, I prefer that the implementation not
be permitted to abort at run time unless it issued a warning for that
specific violation prior to executing the program.
Then this reduces to a quality of implementation issue---users can pick
the implementation that most often exhibits the behavior they like.
Kent
_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
