You don't say if you're doing web based apps or console based apps?
If web based, I'm a big fan of CGI::Application - where it's the controller, your model is a package that defines your user object and the view is whatever template system you choose.
You really don't want to wrap the three parts of MVC into a single OO hierarchy but you could wrap the three individually into seperate OO hierarchies.
In practice, my controllers have always been simple derived classes of CGI::Application (I prefer to have logging embedded into the controller). The model is where I tend to get a bit crazy but it all depends on what your modelling. If you have only one user type than your model can be simply one class. The view has always been pretty simple too but then again I eschew most of the power of my template system (HTML::Embperl) and prefer a USES relationship for my template parts (headers, footers, sidebars, etc) to an ISA one.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||