Frank Wiles wrote:
On Mon, 30 Jan 2006 18:32:13 -0600
JupiterHost.Net [EMAIL PROTECTED] wrote:
a) new CGI is old
FYI...
Just downloaded the latest CGI.pm and the docs still show using
this syntax, as much as I agree it should always be CGI-new();
The docs are old and need
On Tuesday 31 January 2006 08:35 am, JupiterHost.Net wrote:
If it looks like Perl 4 and works like Perl 4 its prolly from Perl 4
(pronounced at least needs to be checked since it may indicate the
problem)
new Whatever;
will work but its highly recommended for various reason to do
Can someone point me at docs as to why that's better? I've seen both used and
didn't know one was considered better than the other.
new CGI; is ambiguouse (did you mean to call the function new() in the
main:: name space with the expression (function? constant? bareword?
handle?) CGI?
With PerlRun, after the script has run the name space is supposed
to be flushed of all variables and subroutines. Right? This doesn't seem
to be happening with my setup. I'm getting incorrect output, based on
previous executions of the script. Here's a simple example:
#!/usr/bin/perl -w
use
On Mon, 2006-01-30 at 17:23 -0600, Patrick Kennedy wrote:
With PerlRun, after the script has run the name space is supposed
to be flushed of all variables and subroutines. Right?
Not exactly. It clears the symbol table that the script uses. It
doesn't touch lexical (my) variables, since those
On Mon, 30 Jan 2006 18:32:13 -0600
JupiterHost.Net [EMAIL PROTECTED] wrote:
a) new CGI is old
FYI...
Just downloaded the latest CGI.pm and the docs still show using
this syntax, as much as I agree it should always be CGI-new();
-
Frank Wiles [EMAIL
