Think about Loose Coupling | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Considering the modules you've already listed, it sounds like you're doing at least some web-related/CGI work with Perl. If that's the case, I'd definitely insist on getting intimate with at least one templating system. I use HTML::Template, but I know that Template Toolkit and Text::Template are also among the most popular. Separating layout control from code control is a good paradigm. And if you happen to be collaborating with designers, it also keeps them happy (and out of your code). I finally started into templating about 6 months ago and have never looked back. It's the easiest step you can take to make your CGI applications more maintainable and less ad-hoc. Search around the monastary for 'templating systems' or similar terms -- there a lot of great templating solutions out there, as you'll see, and everyone has his or her favorite.
For DBI work, I also consider a module such as Class::DBI to be a near-essential. I use a self-rolled equivalent of this module, and it makes interfacing with the data much friendlier. Unless you are doing very complicated database querying, Class::DBI will make coding much faster. These are pretty basic modules that even unexperienced Perlers should be able to handle nicely. I've never used Config::General or Parse::RecDescent personally, but I hear other monks bring them up all the time, so you may find these useful as well. These are the only general-purpose modules I can think of off the top of my head, but I'm sure you'll get a ton of additional replies to this good question. blokhead In reply to Re: Essential Perl Modules
by blokhead
|
|