Brian Mastenbrook scripsit: > > Just to mention that I'm not entirely attached to this. For me, > > it's also reasonable to signal an error when reference to an > > undefined identifier is found. That would require that people > > write recursive procedures "together", or wrapped in a begin, > > instead of being able to type them sequentially. Signaling an > > error also gives more predictable behavior that's consistent > > with R6RS programs (e.g., one may think of every chunk entered > > into the repl as an R6RS top-level program that imports everything > > from the repl environment and exports everything back), at the > > expense of pissing more people off :-). > > This won't bother me a bit. I think it's natural that mutually > recursive definitions should be lexically joined somehow.
That's fine when a calls b and b calls a, but not so fine when the reference loop is many steps long, and you have to either wrap everything in begin or letrec, or else rearrange the natural flow of your program. -- "The serene chaos that is Courage, and the phenomenon [email protected] of Unopened Consciousness have been known to the John Cowan Great World eons longer than Extaboulism." "Why is that?" the woman inquired. "Because I just made that word up", the Master said wisely. --Kehlog Albran, The Profit http://www.ccil.org/~cowan _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
