Reducing design times can be a good thing, but not at all costs.

I agree. But the "not at all costs" goes for a lot of things ;-) So it was implied, at least in my mind.

We are not interested in how fast our code is?

Who is the "we" here? Perl Mon(k|ger)s? That's not really your average Perl programmer, is it? In my experience, people only start to worry about efficiency when they have to wait for it when they feel they shouldn't have to wait for it.

..if the need arises I can always change it for code to be reusable (which if the code is simple and modular, not to hard)...

To me, that means you already have taken re-usability into account. Because you make your code modular. Many, many (bad) Perl programmers do not even do that. The simple fact that you use named parameters to subroutines, might be considered catering for re-usability in my book.

This (needing a test-suite, ed) sounds simple, but this is very, very hard.

Yes, but is that a reason not to build test-suites? Without the extensive test-suite that Perl has nowadays, many, many other bugs were caught before 5.8.1 was released. That the fork/srand bug wasn't spotted, was simply because no one had bothered to write a test for it in earlier versions of Perl. Even though specific code was made in earlier versions of Perl to ensure children would get different random sequences. Fortunately, tests are added to test new aspects of Perl whenever they are added to Perl nowadays (generally speaking), but one needs to remain vigilant in that aspect ;-).

... watch the people howl that it's not a "solution in Perl"

I generally don't watch those people. ;-) And whether people howl in the Monastery over a piece of code, is not an indication by itself of good or bad code. "Think for yourself!" ;-)

Liz

In reply to Re: Re: Re-use: moderation please. by liz
in thread Re-use: moderation please. by BrowserUk

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.