The Problems of Perl: The Future of Bugzilla
aaron.trevena at gmail.com
Sun May 13 15:24:35 UTC 2007
On 13/05/07, Nick Barnes <Nick.Barnes at pobox.com> wrote:
> At 2007-05-12 10:08:02+0000, "Aaron Trevena" writes:
> > IME that isn't true. Mitigating for Python's poor error reporting,
> > Ruby's poor performance and or reinventing wheels in Ruby are costly.
> A number of people have mentioned the quality of error reporting as a
> strike against Python. Can any of these people provide a concrete
> example of what they are talking about? With source code, and a
> misleading or confusing error message?
...because I keep a file of such things to hand.. not ;)
from memory :
syntax error at Line XXX
> I've never had any problem understanding or using Python error
> messages. They're much like Perl errors: you get an error message, a
> code location, and a backtrace.
Except in Perl I'll get a whole lot more, such as 'expected foo' or
'unexpected foo' or 'undeclared bar' or 'runaway quote at line xxx',
and even warnings like '= in selection at line xx'. Perl will always
give a good indication of what the error was in the syntax, python IME
as for debugging.. did you ever bother to are tee eff em?
perldoc perldebug recommends reading perldoc perldebtut and gives the
very simple example of : "perl -d -e 42"
Kinda makes sense, perl -e do evaluate, perl -w to warn, perl -c to
compile, so very arcane, not ;)
LAMP System Integration, Development and Hosting
More information about the developers