Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I think there are several advantages to breaking up the lotsa-modules structure you have
  • you get to think about exactly how all the parts relate to each other
  • whilst they may not be candidates for CPAN, you can create localised 'general' modulues - I find I end up with three groups -
    1. core
    2. tools/utils
    3. specials
  • there are opportunities to refactor/simplify
  • your release process can be better defined - this release is based on fixes to library A and extensions to library B, instead of we changed a whole bunch o stuff
  • because the libraries are separated, one would hope that over time opportunities to use some of them for other projects would emerge - if they are all in one, that step may not be made
  • it shows a level of maturity in your's and the codes development

As for the versioning I use the $VERSION string too, but sometime I even create a file for a library, whose only job is to hold the master version identity of the library. I sometime link this to the CVS version support via
$VERSION = sprintf("%d.%2d", q$Revision$ =~ /(\d+)\.(\d+)/);
or I link to a tag holding the master version identity in CVS via
$VERSION = sprintf("%d.%2d", q$Name$ =~ /(\d+)_(\d+)/);
Be aware that $Name requires you checkout with -r <tagname>, and that CVS doesn't allow you to put '.'s in tagnames, that's why I use the '_' character.

In reply to Re: non-CPAN module distributions by leriksen
in thread non-CPAN module distributions by mp

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (6)
As of 2022-05-28 21:10 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (101 votes). Check out past polls.