Clearly there are Perlish way to do things when you code in Perl and Java'ish way to do things when you code in Java. While there might be common paradigms (we should remember that Perl is a compilation of various 'better' practices initially introduced in other languages), I feel for the most time it is best to not run across the border too much.
Having said that, I don't think it's a good idea to wrap any tiny Perl script around a bunch of OO objects. There is a time and place for every approach. Java, however, was so designed as to rely heavily on OO and work in that 'framework'. Unlike Perl, in Java existence outside an object/class is not possible. In many aspects I sympathize with this approach. On the other hand, however, the task of devising proper OO structures for every little problem/script is at times daunting.
Speaking of naming, I recall it is a norm to see Java packages named as 'so.and.so.and.such' - basically, have multiple nested packages/classes. Whereas this works for Java, I don't see this deep nesting being useful in Perl. This partly stems from the fact that in Perl the number of 'core' objects is significantly less. Instead, in Java, everywhere you look is an object. Hence, the complex package naming scheme. A similar approach in Perl is simply not warranted. The need for a similar naming convention was engineered out of Perl (it doesn't rely as heavily on objects and etc).
_____________________
# Under Construction
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.