Joseph,
I am dealing with error messages one by one, in the order encountered..
This is the last error I received.
Software Errors:
03/10/2003:
What? - Bareword "LINE" not allowed while "strict subs" in use at
guestbook.cgi line 23.
Execution of guestbook.cgi aborted due to compilation
errors.
***********
03/09/2003:
Fixed - Can't find string terminator "E_FORM" anywhere before EOF at
guestbook.cgi line 205.
***********
03/09/2003:
Fixed - Global symbol "$__START__" requires explicit package name at
guestbook.cgi line 29.
***********
03/09/2003:
Fixed - Modification of a read-only value attempted at
/usr/lib/perl5/5.6.1/vars.pm line 40.
BEGIN failed--compilation aborted at guestbook.cgi line 18.
I have no idea what is worng with the syntax $START - LINE;
Should I change the other references to line to uppercase or
(see * ).
Horace
Line 23 - eval { main() }; $START = LINE;
* $START = $LINE
if ($@) {
chomp($@);
$@ =~ s/\(eval\) line (\d+)/${CGI} . " line " .
*$@ =~ s/\(eval\) $LINE (\d=)/${CGI} . " $LINE "
($START-$1-1)/e;
$@ =~ s/( at ).*( line )/$1${CGI}$2/;$
*$@ =~ s/( at ).*($LINE)/$1${CGI}$2/,$
----- Original Message -----
From: "R. Joseph Newton" <[EMAIL PROTECTED]>
To: "Mr. Horace Franklin Jr." <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, March 09, 2003 3:55 PM
Subject: Re: CG I Script [guestbook.cgi]
> "Mr. Horace Franklin Jr." wrote:
>
> > Rob,
> > Disregard the email below.
> > I have one error:
> >
> > Software Error:
> > Can't find string terminator "E_FORM" anywhere before EOF at
> > cgi_guestbook.cgi line 205.
> >
> > The code looks good to me. What does this error mean?
> >
> > Horace
>
> Is this the first error message returned by the interpreter? If not, it
is probably meaningless. The one use of heredoc <<E_FORM in your code [as
posted at the base of this thread] does seem to be properly terminated. The
line numbers are way off, though. This is an indication that you have not
dealt with earlier errors. These earlier errors will often make it
impossible for the interpreter to properly parse code found later.
>
> What is the full message returned on compilation? What do the lines
referred to in the first error message, and the lines just preceding those,
contain?
>
> You MUST deal with error messages one by one, in the order encountered.
Otherwise you are set adrift in a sea of consequential incomprehension.
>
> Joseph
>
>
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
