This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
religious wars
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'my imaginary friend is better than yours'" <cygwin-talk at cygwin dot com>
- Date: Mon, 11 Jun 2007 19:43:34 +0100
- Subject: religious wars
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
A comment that I'm going to remove before I check-in:
+ /* You know,it would look absolutely nonsensical( or perhaps
+ that's just my opinion )if we were to write comments( or
+ anything else human readable )in this style( wouldn't it? ),because
+ brackets go with the content that they bracket,not with the things
+ that they separate their content from,and a punctuation mark does
+ not come with an implicit space.Does it?So why should code be
+ written in this ungainly style?*/
... because although I really dislike the ...
if( arg )
x = FuncCall( arg );
... style and much prefer the GNU ...
if (arg)
x = FuncCall (arg);
... style (and anyway, just exactly which direction do brackets bind in in C,
anyway, eh?), I just really can't be bothered with the long and inane
discussion that would no doubt ensue.
Gah.
Guess I'll just have to put up with my eyeballs being offended.
It does lead me to wonder, though, if there isn't a market for a cross
between CVS and GNU indent that transforms the code on check-out and check-in,
so that anyone who checks out a sandbox gets the files formatted in their own
favourite style, and can write code however they most prefer, and everyone
else sees it in /their/ own favourite style, and nobody even has to know or
care what the actual underlying format looks like at all.
cheers,
DaveK
--
Can't think of a witty .sigline today....