I left out PRE tags because they were listed twice in the line about CODE tags and I wanted to emphasize the use of CODE tags so having PRE tag listed 3 times versus code tags only twice seemed wrong, (I admit I was tempted to leave PRE tags out entirely but decided not to for the very reason you pointed out). As for why did I list them in the order I did? No better reason than I was trying to mimic Vroom
s original showhints() order.
Once again though for many of your points and the others listed (well, the supersearch one is an entirely different question as it requires changing a different piece of code) while excellent they just dont work out for space reasons. At some point theres a tradeoff between pointing something out in the space that will be seen and putting in so much that half of it is overlooked.
Still your point about the code tags susggestion going first (my origianl plan intil I noticed it changed the current order) is a good one and if I find a minute perhaps Ill give it a whirl to implement some or all of the suggestion you and everyone else gave.
Yves / DeMerphq
When to use Prototypes?
Advanced Sorting - GRT - Guttman Rosler Transform
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||