I find your justifictions for giving up Perl in favour of some cut down and simplified look-a-like, that meets with your personal approval, completely unpersuasive.

Just because you feel the need to single step through every clause and condition of your code in order to debug it, does not mean that everyone needs to resort to such primitive measures.

And if the time required to convert a single statement with a post condition into a pre-condition block with two statements, is a significant portion of the time it takes you to decide that it needs to be done, it probably expains why you spend so much time debugging.

And I find your suggestion that anything like a majority, or even a major minority of the programmers in this world need to have their code delivered in bite-sized morsels unproven. And frankly, vaguely insulting.

Imagine music without the black notes Cos thirteen are harder than eight to learn Or written without the use of chords Cos multiple tones are hard to discern Further, and just for good measure Imagine that just one meter was used Ev-ery thing would be mo-no-ton-ic Then no one would ever be confused.

Care to post a semi-substantial piece of your code? I'll re-write it to my standards, and then we can have a proper discussion about maintainability. And if you've any balls, you'll quit hiding behind anonymonk.

In the meantime. I should have stuck to "Just saying .."


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^4: "my $p = value if condition()" as bad|deprecated as "my $p if 0" (Naughty indeed) by BrowserUk
in thread "my $p = value if condition()" as bad|deprecated as "my $p if 0" (Naughty indeed) by parv

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.