As has already been mentioned, CPAN has scripts. But the next logical question is, does it need to be a script? You could modularise it, and then have a script in your distribution that called the module. And that may make it easier for
- others to modify it,
- others to extend it, and
- others to use it in wierd and wacky ways (e.g., convert a word file during upload as a filter for a CGI script directly into a TWiki hosted on the same, or different, machine, without actually using a temp file).
Then you may think CPAN makes logical sense. As for a repository for your code elsewhere, outside of your personal machine,
Sourceforge makes as much sense as anywhere else, especially if you already have an ID there. If you don't, then it probably doesn't matter - pick a place and use it.
Of course, I'm one to talk - I do have an account on Sourceforge, but none of my perl code is up there. :-) I keep meaning to do it ... just never get around to it.
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.