Front page | perl.perl5.porters |
Postings from April 2000
At 08:11 AM 4/4/00 -0600, Tom Christiansen wrote:
> >Would a satisfactory approach be for the error message to be couched in
> >terms of the source,
>
>Perhaps, except that we're talking interpreter warnings, not compiler
>warnings. The compiler knows about three-part for loops; the
>interpreter does not. Likewise, the compiler knows about string
>and array and slice interpolation; the interpreter does not.
Then we need to either:
A) Post in big bold letters someplace that internal optimizations may make
the errors they get at runtime a little odd
or
B) Attach enough hint info to the optree to emit errors correct for the
original program text
A's easier, B's better but more expensive both in compile time and porter
time. If the optimizer gets seriously attacked, though, it might be worth it.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
dan@sidhe.org have teddy bears and even
teddy bears get drunk