It there would not have been this slang (for me), this module - as it currently is - would not have happened at all. So what is better/worse?

Years ago I took a contract in the IT dept. of a very large, UK retailer renowned for doing things "their way". The code was in C; the platform OS/2 and their coding standards, whilst not extreme; slowed me down and frustrated me enough to seek a solution. (For more details and an amusing story see one of my earliest posts here.)

The upshot of which is that I used a C-beautifier and some editor macros to convert the house style to my preference when loading a source file; and back to the house style when saving.

This simple expedient allowed me to type my code utilising muscle memory; and more importantly to read code in the style to which I was accustomed; thus maintaining my productivity and avoiding a lot of frustration.

I fear that by building the stylistic adaption into the language, rather than providing an external tool to 'port' styles through a common set of choices, the result will be that a few years down the road when modules have passed through the hands and brains of many maintainers, it will end up being a hotch potch of different styles on a block-by-block basis enabled through the use of lexical pragmas.

That's a world of pain that I have no desire to have to maintain.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
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". I'm with torvalds on this
In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

In reply to Re^5: Porting (old) code to something else by BrowserUk
in thread Porting (old) code to something else by Tux

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.