I agree, BrowserUk, that's why I said to the OP that it was her or his decision, based on her or his knowledge of the process. Most of the programs I write nowodays are run typically once per month, but, on the other hand, they handle very large volumes of data (usually tens or hundreds of GB) and may take long times to run. I have to make sure my programs are efficient, to make sure that they don't take days to complete, and I take great care making my algorithms efficient, and that can make quite a large difference (and that is important to me because the people running my programs are often part of my team), but, on the other hand, gaining a few seconds on a micro-optimization is not worth the effort if the rest of the program is taking 2 hours to run. Sometimes, on the other hand, a micro-optimization is a real win, for example if it applies on an operation that will be executed billions of times. I had a couple of cases in the past year where it really made sense to think at the micro-optimization level (and at least one case where I changed from a regex to unpack), but most of the time it does not cxut a real difference. Again, the decisions to carry out optimizations should be based on a good knowledge of the business process; sometimes they are really woreth it, sometimes not.

In reply to Re^5: How to convert between decimal and binary for negative numbers? by Laurent_R
in thread How to convert between decimal and binary for positive/negative numbers? by thanos1983

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.