Adding to what others have already said:
CGI.pm implements its own autoloading scheme, which means that no function is loaded until you need it. This means that in normal use the module is actually a lot slimmer than it might look.
As for the namespace issues. I always use the procedural interface which gives me complete control over the functions imported into my namespace. Given that most of my HTML is going to be stored in some kind of template, many of my CGI scripts start like this:
use CGI qw(param header);
as those are the CGI.pm functions that I'm going to use.
Having said that, I do think that if the HTML functions were pulled out into another module so that CGI.pm just dealt with the CGI protocol, then that would be a good thing.
--"The first rule of Perl club is you don't talk about Perl club."
In reply to Re: CGI made me bloated
by davorg
in thread CGI made me bloated
by mattg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |