Dan Sugalski writes: > No, that's the point. But if someone explicitly strips out the debugging > info then, well, you don't get much help in debugging, now do you? :) I buy that. It'd be nice to be able to be one step better than C, though, and given *something* that you can use to go back to your source from. Nat
- RFC 214 (v1) Emit warnings and errors based on unoptim... Perl6 RFC Librarian
- Re: RFC 214 (v1) Emit warnings and errors based o... Nathan Wiger
- Re: RFC 214 (v1) Emit warnings and errors bas... Simon Cozens
- Re: RFC 214 (v1) Emit warnings and errors... Nathan Torkington
- Re: RFC 214 (v1) Emit warnings and er... Dan Sugalski
- Re: RFC 214 (v1) Emit warnings a... Nathan Torkington
- Re: RFC 214 (v1) Emit warnin... Dan Sugalski
- Re: RFC 214 (v1) Emit wa... Nathan Torkington
- Re: RFC 214 (v1) Emit warnings a... Steve Fink
- Re: RFC 214 (v1) Emit warnin... Chaim Frenkel
- Re: RFC 214 (v1) Emit wa... Dan Sugalski
- Re: RFC 214 (v1) Emit wa... Tom Christiansen
- Re: RFC 214 (v1) Emit wa... Dan Sugalski
- Re: RFC 214 (v1) Emit wa... Chaim Frenkel
- Re: RFC 214 (v1) Emit warnin... Bart Lateur
- Re: RFC 214 (v1) Emit wa... Steve Fink
- Re: RFC 214 (v1) Emit wa... Dave Storrs
- Re: RFC 214 (v1) Emit wa... Steve Fink