> Is there ever a case in the current day to write a module that isn't OOP. The discussion has certainly answered that there is.
Yes!
Not everything has to be OO.
That's why I enjoy Perl and C++; their designers appreciated that OO is not necessarily the best solution
to all problems.
As an aside, I was once hired as a Java programmer but
its emphasis on OO felt oppressive and I quit soon after (as mentioned here).
Though I managed to hold down a C job without resigning,
I didn't enjoy its primitive abstractions (for example, compare this rosetta C function with the other languages!)
nor its flawed standard library, such as strtok, singled out for a dishonourable mention at On Interfaces and APIs.
I suppose that's the main reason I gravitated towards C++ and (later) Perl.
(BTW, Stroustrup describes here
why he designed C++ as a multiparadigm programming language).
> I know there are Text::Info and Lingua::EN::Fathom. The latter I am using to create a copy checker that also includes a ratio of first person to second person pronouns. Both these modules count syllables using Lingua::EN::Syllable.
Rather than starting from scratch, you might like to model your new module on your favourite from these three (they all seem to have decent authors):
- Lingua::EN::Syllable by Neil Bowers. I see Neil (aka neilb) is from Marlow UK, a short scenic drive from your (more working class?) Coventry UK. Neil is a prolific CPAN author ... and a PAUSE Admin, PSC member, and White Camel award recipient!
- Lingua::EN::Fathom by Kim Ryan. I've actually met Kim - he's an excellent programmer, a gentleman (and a gentle man) ... and the founder of Sydney.pm.
- Text::Info by Tore Aursand. I'd never heard of Tore before, but I see he's published nine CPAN distributions. Though the name suggests Scandinavia, I trust you're willing to forgive and forget the Norman Conquests. ;-)
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.