As derby suggested, the param() method of CGI::Application is not what you think it is.
The param() method ... Let's say it was designed with order and organization in mind. So where in other oo type modules you may have object params in $object->{property_x} or $object->property_x, in CGI::Application objects you would hav e this in $object->param('property_x').
(This used to be annoying to me. But.. hold on, it'll make sense later on. I suggest you trust it.)
So, if you want a param as we think of it, as from a form submitted, etc..
Instead of the usual cgi script..
my $cgi = new CGI; $cgi->param('name');
You can just..
$cgiapp->query->param('name');
This is good. Because for example with CGI::Application::Plugin::Session.. you have..
$cgiapp->session->param('name');
and so.. if this were also in the cgi app instance (the object..)
$cgiapp->param('name');
This is cool later on as code gets hairy.. it provides some consistency.
In reply to Re: CGI::Application, $self->param() doesn't return
by leocharre
in thread CGI::Application, $self->param() doesn't return
by flamey
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |