Not only would CPAN need to compile the file, but also
run it, as $VERSION is typically set at compile time.
CPAN is not going to run the entire file.
What I'm trying to avoid is all the CPAN problems to which you allude: all the files in my package remain in lock
step through every release (and reflect the version of the overall distribution).
Whether your files remain in lock step is not archieved by
inheriting $VERSION. What you do lose is the
ability to easily check whether your files are in lock step.
If each file has its own $VERSION, it's easy
to see if there's a mismatch. If they inherit from a single
source, there's no way to find out.
IMO, if you inherit $VERSION, you'd lose one of
major reasons to use a version number.
Abigail
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.