There's readable and then there's readable. For example, compiled C programs are extremely difficult to decompile - generally if you're going to do that your time would be better spent reimplementing it yourself. But Perl is different. PerlAPP, Perl2EXE and
PAR all function, albeit in slightly different ways, by bundling the Perl interpreter and your Perl source code into a single .exe file. This means that with only a moderate amount of work, someone can pick apart that exe and extract the original source - it's not even decompiling at all really. Bearing that in mind, I wholeheartedly agree with the suggestion that what you really need is a solid licensing agreement.
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.