The apparently arbitrary restrictions, are very far from being arbitrary.
There's nothing wrong with using modules (I use many myself),
but as a perl nub, an "I want X done" isn't my entire interest, but a more "how does it work" wondering,
both for theoretical and practical purposes.
Also the more fundamental the code is, the greater its implementation potential is,
the less likely it is to surprise the user (by run/intent errors), and the easier it is to be customize to the exact desired purpose for which it is required.
A less common reason to avoid modules (I faced) is when planning to convert the pl file to something else (like exe) once it's done,
but your converter can't handle modules correctly.
Generally when writing a long and complicated program, a module can be a huge time (& headache) saver,
but whenever using a module can be avoided (with a reasonable cost), a diy is always my choice.
| [reply] |
| [reply] |
I've tried:
* perl2exe of indigoStar
* the pp module
* Cava Packager 2.0
the last one seems to work with modules but it makes the exe huge in size for no obvious reason.
I've actually asked about the perk2exe topic several times but never found an idle (& free) solution.
| [reply] |
