db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Maes - Materialogic Programmer <jm...@materialogic.com>
Subject Re: Code formatting debate, confusion and wasted time , Has it gone on long enough?
Date Thu, 01 Jun 2006 01:57:08 GMT

As just a lurker on the list, I'm not sure that I should even offer 
anything here, but what's the fun unless you have your poker in the 

I'll avoid throwing any weight (i have none, remember the lurker 
status) behind one coding style or the other (TABS must DIE [note, this 
doesn't count as weight in any form due to the aforementioned avoidance 
clause]), but I do have something that might help (other than :set et<cr> 
:set ts=4). 

I've had to draft several somewhat formal coding standards for different 
projects / companies and would be more than happy to throw one out there 
as a starting point.

It covers most things and a few others as well. 

I'm sure that when burned, it will create flames at least hot enough to 
make me run screaming back into lurkersville. 

If interested, I would be happy to post a version of it in all the 
needed formats.

Also, I am well aware that anything i find remotely funny is far from 
anything that anyone else finds remotely funny(in case you found something 
funny or something un-funny above [Note - I'm funny, everyone else 
is troubled]), but I find hope for the others, as the great W.S.C said, 
never, never, never quit (he drank enough 
to kill a small donkey most days....)


On Thu, 1 Jun 2006, Dag H. Wanvik wrote:

> Andreas Korneliussen <Andreas.Korneliussen@Sun.COM> writes:
> > 3) A file should be consistent in its use of spaces vs. tabs. If a
> > file uses spaces for indentation, no tabs are allowed into that file.
> >
> > The problem with rule 3, is of course that developers need to set up
> > their tools based on which file they are modifying. It is easier if
> > all files have the same indentation-style. Therefore I support getting
> > a well-defined code-format in Derby.
> +1 
> I support that should agree on a standard for whitespace, I am tired
> of the current situation.
> My vote would be for spaces rather than tabs (most editors, and IDEs
> can be persuaded to do that), for the reasons quoted by Bernt and
> Andreas and others. It is also easy to enforce/check for committers.
> I would also vote for keeping 4 as the normal indentation amount,
> although I consider that less important than the tabs vs whitespace
> decision.
> As for the concerns of inconvenient historic blame/praise information
> (before homogenization and after), I think this is the price we will
> have to pay sooner or later. I also think Kathey's suggestion of a big
> bang makes sense (lesser evil compared to piece-meal conversions).
> A coding standard for code layout will get my support as well.  I am
> happy to work with any style as long as it is consistent, but it is
> just that much easier to be consistent when changing someone else's
> code if we have one common standard, in stead of one per developer.
> Dag

View raw message