Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

xsawyerx (8978)

xsawyerx
  (email not shown publicly)

Journal of xsawyerx (8978)

Sunday August 02, 2009
02:25 AM

Descriptive errors?

[ #39390 ]

I love that Perl (5 and 6 even more) is so in tuned with programmers, that when I have an error, I know the actual reason of the error. I can make a mistake and Perl would say "You probably meant to do THIS instead.." instead of saying "Assignment failure".

Subversion says "svn: Can't find a temporary directory: Internal error" when it actually means to say "Uh.. I seem to ran out of space on the subversion server...".

I can't compare Perl to Subversion as languages because Subversion isn't a language, but I can definitely compare them as programs and projects that rely on communities and user insights. Perl really shines in that aspect.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I agree. diagnostics [perl.org] and perldiag [perl.org] are both very nice in that way.

    -- dagolden [dagolden.com]

  • The situation with Perl's warnings and errors is not always so rosey. For example, with this program:

    #!/usr/bin/perl

    use strict;
    use warnings;

    $name = "Sophie";

    print "Hello $name!\n";

    We get:

    Global symbol "$name" requires explicit package name at test.pl line 6.
    Global symbol "$name" requires explicit package name at test.pl line 8.
    Execution of test.pl aborted due to compilation errors.

    After years of using use strict I got used to the fact that it means that I haven't declared the variable using a "m