Seeing code should not be a security risk. Your code should not contain embedded passwords, etc. Also, the Open Source movement has shown that open and available code, combined with a mechanism for others to review and submit changes to that code, results in better security (in general).
The reason script source isn't available is rather one of these:
- The source embodies a trade-secret or some sort of intellectual property.
- Script-capable web servers are configured to execute that code, so no mechanism is in place to simply tranfer it -- putting the file up in a downloadable form is an extra step, and most people simply don't bother.
- The code is either trivial or publicly available from a different forum (e.g. the Scoop code that drives Kuro5hin has its own site, so Kuro5hin doesn't publish it on the main site).
Larry Wall is Yoda: there is no try{}
The Code that can be seen is not the true Code
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.