Yes, the Java environment is so fundamentally different from Perl that concepts will not transfer easily nor directly from one to another. I would look instead at venerable Perl implementations – DBI very specifically comes to mind. But also, "keep your boots on the ground," which means always knowing what and where the ground is. There is such a thing as over-abstraction, and so your design decisions need to keep concrete implementations in mind. Also consider the many ways in which JSON functionality have been tackled – notice how there are both XS and Pure Perl implementations of things. Also notice how sometimes the onus is upon the individual package consumer to choose a concrete package, whose API might merely be similar among several different concrete alternatives. It is rarely productive to go so far as to say that apples and oranges are abstracted-away as fruits. Perhaps it is good enough to implement several packages with a mostly-identical API and leave it to the consumer to decide which one to use, expecting him also to perhaps take advantage of the slight-differences that you have thoughtfully provided.

In reply to Re: perl module structure by Anonymous Monk
in thread perl module structure by pwagyi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.