Re: [CGI ERR] Global symbol requires explicit package name ...

2002-10-18 Thread fliptop
On Wed, 16 Oct 2002 at 19:33, Colby opined:

[snip]
C:Global symbol  requires explicit package name at ./myscript.cgi line
C:60, 70, 90, 108
[snip]
C:I've gone over the code with a fine-tooth comb as it were, checked for
C:the usual (missing semi-colons, right parenthesis/curly braces, etc
C:...) and found nothing amiss.  I haven't run the script through the
C:Perl debugger yet and I am not able to do so on the web hosting
C:company's server because they don't allow telnet/SSH.

how long is the code?  it would help if we could take a gander at it.

perhaps you could try another small test script and see if it does the 
same thing (if your original script is too long)?


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




[CGI ERR] Global symbol requires explicit package name ...

2002-10-18 Thread Colby
I have a CGI script accessing a MySQL DB via DBI, the script executes
almost flawlessly on my home Linux box running Apache 1.3.26 and Perl
5.8.0 (with the usual modules installed and then some :)  (The only
complaint my computer gives is a warning related to the concatenation
operator '.')

However, the web host that I've just signed up with (running RH Linux
with Apache 1.3.? and Perl 5.6.1) won't execute my script and returns
the following errors when run from the command line:
_

Global symbol  requires explicit package name at ./myscript.cgi line
60, 70, 90, 108
_

I understand that that error usually means that when using '-w' and
'use strict;' that I haven't declared a variable using 'my $varname;'
I don't have a variable that has no name or is  and so the above
error has really stumped me.

I've gone over the code with a fine-tooth comb as it were, checked for
the usual (missing semi-colons, right parenthesis/curly braces, etc
...) and found nothing amiss.  I haven't run the script through the
Perl debugger yet and I am not able to do so on the web hosting
company's server because they don't allow telnet/SSH.

Any ideas folks?

Thanks in advance.



-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]