Depends on what was going on -- was it mixing get and post, frex? CGI.pm will happily parse both get and post -- but on a post request, it will only make the post options available -- the query string options (if also existent -- usually because they're in the form action) will be parsed but not made accessable unless requested. Not sure what else would generate the behavior described.
Perl is actually a remarkably elegant language -- for one that's as big as it is. (that said, there's a lot of accumulated cruft, some of which isn't really as useful as originally intended -- like the mutating funny characters on the beginnings of variables, and the related differences in the syntax for accessing a thing and for accessing a reference to the very same thing. Much of this will change in perl 6).
But CGI.pm is a bloated and over-ambitious tool, and one I'd not normally recommend using -- you're better off using a smaller CGI library that doesn't try to also handle HTML creation -- or just jump to mod perl, depending on your platform.
no subject
Perl is actually a remarkably elegant language -- for one that's as big as it is. (that said, there's a lot of accumulated cruft, some of which isn't really as useful as originally intended -- like the mutating funny characters on the beginnings of variables, and the related differences in the syntax for accessing a thing and for accessing a reference to the very same thing. Much of this will change in perl 6).
But CGI.pm is a bloated and over-ambitious tool, and one I'd not normally recommend using -- you're better off using a smaller CGI library that doesn't try to also handle HTML creation -- or just jump to mod perl, depending on your platform.