Steve Fink writes: > I suspect perl can do a much better job than it does now, but if you > make it a requirement, you prevent many optimizations. I think the RFC > should be very specific about when it applies and when it gets out of > the way. I can't be more specific unless I know the optimizations. So I'll fudge and say "unless a compelling case can be made for an optimization that absolutely cannot preserve this information". I don't mind a bloated optree, so long as there's a way to trim it. Nat
- Re: RFC 214 (v1) Emit warnings... Dan Sugalski
- Re: RFC 214 (v1) Emit warnings... Tom Christiansen
- Re: RFC 214 (v1) Emit warnings... Dan Sugalski
- Re: RFC 214 (v1) Emit warnings... Chaim Frenkel
- Re: RFC 214 (v1) Emit warnings and... Bart Lateur
- Re: RFC 214 (v1) Emit warnings... Steve Fink
- Re: RFC 214 (v1) Emit warnings... Dave Storrs
- Re: RFC 214 (v1) Emit warnings... Steve Fink
- Re: RFC 214 (v1) Emit warnings... Chaim Frenkel
- Re: RFC 214 (v1) Emit warnings... Dan Sugalski
- Re: RFC 214 (v1) Emit warnings and... Nathan Torkington
- Re: RFC 214 (v1) Emit warnings and errors b... Chaim Frenkel
- Re: RFC 214 (v1) Emit warnings and errors b... Dave Storrs
- Re: RFC 214 (v1) Emit warnings and errors based on unopt... Dan Sugalski