why the different handling of arguments re: command line vs CGI -- and where, if anyplace, is that documented?
A good place to start is the CGI spec, but to answer your Perl isn't a CGI-centric language, so there's no reason why command-line and CGI arguments to be handle the same way.
Heck, if you happened to write a Perl based webserver, handling them the same way could be detrimental; after all, how would you pass arguments to the webserver and process CGIs?
could you possibly explain the REALLY bizarre CGI response
An oversight on my part:
If CGI.pm thinks it's being called ISINDEX-style (see the spec again and the CGI.pm's keyword section) it behaves a little differently, making arguments available via keywords or param('keywords').
Something like the below may get things working as you expect, but my testing was inconsistent across different versions of CGI.pm.
if ( param($key) ) { foreach my $value ( param($key) ) { if ( $key eq 'keywords' && keywords ) { # We ONLY have booleans push @ARGV, param('keywords'); next; } push @ARGV, $key, $value; } } else { # ...
--k.
In reply to Re: Re: Why does Getopt::Long ignore browser and SSI-based parameters?
by Kanji
in thread Why does Getopt::Long ignore browser and SSI-based parameters?
by ayurkowski
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |