better read some Perl :)

Juerd thats a big load of hoo-hoo and you know it.

most occuring idioms,

Do a grep of site/lib and you'll see just how common that idiom is. I think youll be suprised.

Anyone who doesn't see it's a constant (single return value, empty prototype, name in ALLCAPS, defined before any other sub and often found in @EXPORT), should not be maintaining my code.

The fact is that these "constants" (they arent really so lets be careful with that term) will not behave as expected in about 5% of situations. And you've just demonstrated my point. You didnt even realize what quirks I meant. So if you didn't why the hell would the maintainence programmer? Oh and the other point is that you will almost never have the choice of who maintains your code.

If someone hires a non-coder to do code maintenance, that's not my problem :)

Actually, 99% of the time it will be your problem. It will be your problem when your boss fires you for writing unmaintainable code, itll be your problem when your boss tells you to drop the sexy new project you are working on to do maintainence on old code that has been written poorly, it will be your problem when you stop getting work because you have a reputation of writing unmaintainable code.

Unmaintable code is bad code. Its your job as a developer to anticipate _everything_ including the skill levels of those that come after you. Which you should expect to be lower than your own.

Frankly juerd im a little disappointed about your reply and I think that if you sit back and reconsider so will you.

Yves / DeMerphq
---
Writing a good benchmark isnt as easy as it might look.

In reply to Re: Re: Re: Re: Re: Breaking output lines into N-element chunks by demerphq
in thread Breaking output lines into N-element chunks by FoxtrotUniform

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.