It is not clear however why you don't simply put each perl build in a separate hierarchy
I used to do that, but the repeated duplication of hunks of perl didn't fit well with my frugal nature and my sense of orderliness.
Perl already offered the option to take this alternative approach, so I thought "why not".
I would have gone ahead with the change even if I had been aware of this issue - and I'm still happy that I did go ahead with it.
If it does matter, that suggests either that there are tests missing for Module::B, or that there is code in one module that should be in the other
It's quite possible for bugs to exist for just one architecture - maybe because a pre-requisite is at a different version, or because a need specific to one architecture has been overlooked.
I just want to do what I can to ensure that any such bugs affecting my module are caught.
Cheers,
Rob
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.