in reply to Strange problems with CGI script

Look closely at what you have in variable $c2! 

Unmatched ) before HERE mark in regex m/href.+?>(2345678901234()|.)) <
+< HERE / at C:\test\junk.pl line 55.

[download]

Examine what is said, not who speaks.

The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.

Replies are listed 'Best First'.
Re: Re: Strange problems with CGI script
by Wassercrats (Initiate) on Jan 28, 2003 at 09:23 UTC
    I've had several programmers trying to figure this out, and nobody found that! How does one get to see that error? It wasn't in my error log. Thanks!
[reply]
      Due to various issues people have with error logs, you shoud really debug from the commandline, especially for compile time errors.

      You should also familiarize yourself with CGI::Carp (great for run time errors). I'm quite fond of keeping my own log, something resembling 

      BEGIN {
    use CGI::Carp qw( fatalsToBrowser );
    CGI::Carp::carpout(\*LOGGY)
        if open(LOGGY, '>>'.__FILE__.'.err.log');
}

      [download]

      MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
      ** The Third rule of perl club is a statement of fact: pod is sexy.

[reply]
[d/l]
        That's the best advice I've received (and will take) in a long time! I wish I knew that along time ago! Recently, my web host's server didn't return a fatal error in the error log, but I assumed that was just a web host thing. When others programmers couldn't find this one (and I know they tried), I figured there was no error that would stop execution.
[reply]

In Section Seekers of Perl Wisdom