comment on

I agree in principle about the difference between a 'snippet' and a 'program', but I think that this distinction is easily blurred

There was nothing in rozallin's proposal to stipulate that an entry in Code Catacombs had to be a particular minimum number of lines of code. If a one-liner stands on its own as a useful and reliable tool, then it would belong in the Catacombs. (Meanwhile, some "snippets" could be quite large, despite having limited utility...)

I especially like rozallin's proposed distinction between the functions of "Craft" and "Catacombs" -- i.e. tentative vs. tested code. Note that rozallin used the term "polished", not "finished"; indeed, there is virtually no such thing as "finished" code (except for stuff that no one uses any more).

And because folks can update their own root nodes in the Catacombs section, this is an excellent place to maintain useful tools.

In reply to Re: Re: Re: One Section to rule them all. by graff
in thread One Section to rule them all. by benn

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks