It would be useful to maintain a list of CPAN
modules that have unusual behavior such as Acme::Bleach.
Perhaps MODULATOR could detect these modules and automatically update the list.
If these source-modifying modules all had
antidotes with a common naming convention,
then MODULATOR could check for self
modification and run the antidote if necessary.
I wrote a program to reverse the effects of Bleach.
I called it
If more people give in to the temptation of writing
perl code that has unusual side effects,
validation will grow in importance.
There is potential for harm in many more ways than
modifying source code, as merlyn points out.
A validation program could use checksums, take
advantage of MANIFEST information, etc. It could
also be useful for checking for non-perl applications.
It should work perfectly the first time! - toma
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||