Here's what I do:
I make sure to name all of my subroutines in each file sequentially like "sub s1", "sub s2", "sub s3"... This helps minimize the amount of space the file takes up on disk. Then, so I never lose track in a file, I split all subs into separate files (deleting all comments to save space) and name them sequentially as well, "f1s1.pm", "f1s2.pm", ..., "f1238s13.pm". I store all files right on C: (fewer directories means fewer bytes taken up on my machine) and then I use Google Desktop to search for files when I need them. With 12,462 files, Google Desktop still manages to find what I need in no time at all. I just sift through the ten or twenty results it kicks back until I find what I need and I'm set to go. Most of my files look like this:
use f1.s1;
use f1.s2;
use f1.s3;
...
# about twenty or thirty lines omitted
...
use f132.s12;
if(f1::s3($a,$b)){f12:s3(f3:s2($b)+$a)}
...
What'cha think?
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.