[ CCed to [EMAIL PROTECTED] ]
On Sat, Jun 21, 2003 at 03:20:59PM -0700 Rob Richardson wrote:
> I found out where the problem was, but not why it happened. It occured
> to me that it might be a good idea to compile each of the module files
> my program uses individually. One of them had a missing parenthesis.
>
> I have no idea why the IndigoPerl compiler didn't find it before. It
> was letting the program run. It's a CGI program, and it was throwing
> up an Error 500 screen. The log file was telling of the undefined
> subroutine longmess_heavy and that I had a premature end of script
> headers.
>
> This is the second time I've seen IndigoPerl fail to catch a blatant
> syntax error. I found a simple way to get it to ignore a missing
> semicolon. (Unfortunately, I've forgotten what it is now.) Is
> ActiveState's Perl compiler any better?
I haven't ever used Indigo so I don't know how it compares to
ActivePerl. However, I know the latter and never encountered such a
behaviour with it. It seems odd that the parsing routines in IndigoPerl
should produce results different from other perls because it would mean
that they applied some patches of their own.
Only recently a not so very credible source on comp.lang.perl.misc
stated that there'd be a couple of problems with IndigoPerl 2003.
Obviously your observations go into the same direction.
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
