In the case of an unwanted pregnancy, there's a three way choice: abort; keep the baby; give it up for adoption.

All the choices are wrong, which makes choosing the least wrong one in your particular circumstances very hard indeed.

Choosing your code indentation style is unlikely to have such a devastating effect on the lives of at least two people, but there's a strong case for saying that all the available choices are wrong as well.

The best choice to make is the one your teammates (or your team leads) make. If you have the tools to let you code in your favoured style and then convert back to house style, good for you. If you don't, you live with house style.

So, I have a preference certainly (spaces throughout), but it's not The Right Answer. Nothing is.

Arguing that your way is the One True Way is already laughably futile. Arguing that it's the One True Way because it adds valuable extra metadata, when that 'metadata' can be worked out by any code editor worth its salt (or delegated to perltidy) would appear to plumb the very depths of futility. Well done.

Someone give that man a bathyscaphe.


In reply to Re: Tabs vs Spaces lets give this a go by pdcawley
in thread Tabs vs Spaces lets give this a go by EvanCarroll

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.