“Inconvenient,” perhaps, but not “useless.”
In all seriousness, what is so utterly wrong with just using a subdirectory? Apple’s OS/X system is rather elegant, I think, in taking that approach with how they package all applications: they’re actually folders. Just put your executable together more-or-less as a stub, and put the necessary Perl source modules into a directory in a chosen location.
(When I have done this, I used a nested directory structure: the outer directory contained README.TXT and an inner folder named guts. The entire thing was marked read-only. And the README file contained a message which basically said: “Keep your mitts off that folder and everything that it contains. These aren’t the ’droids you’re looking for.” I got a few whimsical comments about that, so I know that some people read it.) To me, this is every bit as convenient a form of “packaging” as a DLL-file would be, and considerably more maintainable. It might well be more efficient, too, because Windows will routinely use VM-mapped file I/O when working with files.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||