note
ybiC
<p>
<i>caveat: not necessarily a direct answer</i>
</p>
If you're not already using it, [http://www.cvshome.org/|CVS] may be of some benefit in organizing your code, with [http://cvsbook.red-bean.com/|The CVS (free online) Book] being a good tutorial. A Monastery [cvs|search on 'cvs'] also turns up a passel o'hits, hopefully some being relevant.
<br> cheers,
<br> Don
<br> <i>striving toward <a href="http://prometheus.frii.com/~gnat/yapc/2000-stages/">Perl Adept</a></i>
<br> <font size="-2">(it's pronounced "why-bick")</font>
<p>
<b>Update A: </b> to more directly answer your question, I keep current executable versions of my own scripts/programs in a structure pretty much like what you expressed dissatisfaction with, and experience some of those same concerns.
<code>~/bin/bash/
/java/
/perl/</code>
Fwiw, I try to give my scripts/programs descriptive names, to make it easier on my feeble recall. Although this often runs counter to the principle of short-names-for-oft-used-tools. *shrug* In addition, I try to use one-liners when possible, rather than writing piles of throw-away snippets. Seems to help a bit in avoiding clutter in ~/bin/perl/ directory.
</p>
<p>
<b>Update II: </b>
For what little programming I do on Win32, I've yet to need anything more complex than this:<br />
<tt>c:\perl</tt> Perl install of course<br />
<tt>c:\perls</tt> for my scripts/programs
</p>
<p>
Like you, hoping to hear how other other monks do it...
</p>
215367
215367