|but the person I'm writing it for likes the code to be object-oriented.
My personal feeling is that's not their decision to make. OO is not the be-all, end-all. Using OO for the sake of it when it is not warranted is silly.
The technical details of the implementation are up to you as the programmer. Use the right tool. If OO makes sense for the script, use it. Do what is simplest, and most maintainable, and makes sense for the application.
I get into this at work all the time, where management wants to dictate a piece of the technology, where they are not knowledgeable. It needs to be left up to us, the programmers, to make the proper technical design decisions (within reason of course, that doesn't mean telling the company to switch from Linux to FreeBSD just because prefer it or whatever... there needs to be merit.)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||