Front page | perl.perl5.porters |
Postings from March 2000
--- Tom Christiansen <tchrist@chthon.perl.com> wrote: > >Tom Christiansen writes: > > > >I would prefer warnings the way they used to be, if it's that > hard. > > > > > > The "used to be" way was less information. That's just stupid. > If > > > the kiddies aren't old enough to know the truth, tell them to use > > > BASIC. > > >Less information is better than wrong information. > > This is the last time I'm going to say it: it's not wrong > information. > You just don't understand why it's right. There are millions of > cases like this. Ah, I see now. Ok, then, the solution is (in Tom's mind) to append "Please use the Deparse feature so you can understand this message" to every message that might result from optimizations? I'm sorry if I'm extending this argument needlessly, but I think it's just plain _wrong_ to require the end user of a compiler to understand the internal optimizations just to decode the error messages. Especially when many acceptable (to everyone but TomC apparently) alternatives exist. How about making the message "Use of uninitialized value $... on line xxx (in operator . after optimization)". The phrasing clearly needs work :) Then the users at least have a hint as to where the mysterious . came from. -- Mike __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com