Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of rodrigo.madera@gmail.com
 designates 66.249.82.202 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Jegau4ejyPRo5TItaLFLltkUwxn5pJidKn/gnI2V0mh0KWssT62VtT/MZCvjz8buquneIIYu4O3L5yWsuiADw3QgxuQH+JjWo2IgqlUB7fcOqQnzSMSEFqdg4BhogiAkKtuJ6jdznqI6e0Xjfz4i5vfdXwmuKu0+dizHz2Ui+kM=
Message-ID: <3cf983d0606090925g24aa2e07u131605d9190429e7@mail.gmail.com>
Date: Fri, 9 Jun 2006 13:25:08 -0300
From: "Rodrigo Madera" <rodrigo.madera@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: Code formatting debate, confusion and wasted time ,
 Has it gone on long enough?
In-Reply-To: <x1o31wtyix97.fsf@sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <447DA443.3000706@sbcglobal.net>
	 <20060531191838.GB29296@localhost.localdomain>
	 <3cf983d0605311235u2b7ebce3qdf6db491e46b0bb1@mail.gmail.com>
	 <c25576af0605311255q4992eb67ncf41701f4151961a@mail.gmail.com>
	 <447DFBA5.3090500@sun.com> <447E2172.9040401@sun.com>
	 <3cf983d0605311634r43a0fa5fj65af6adb76112aae@mail.gmail.com>
	 <x1o31wtyix97.fsf@sun.com>

So you vote on spaces or tabs anyway?

On 6/9/06, Dyre.Tjeldvoll@sun.com <Dyre.Tjeldvoll@sun.com> wrote:
> Rodrigo Madera <rodrigo.madera@gmail.com> writes:
>
> > One thing there is to learn from all this: Set standards BEFORE the
> > project starts.
>
> Actually, it is not that simple. Derby opted to follow Sun's java
> guidline which, believe it or not, says that if tabs are used, then the
> tabwidth should be 4. Which, of course, is utterly brain-dead.
>
> It would have been much less painful to introduce space indentation
> gradually if the tabwidth had been 8, because then tab and space
> indentation could have coexisted in a file without making the file
> unreadable in most tools.
>
> A file that is consistently indented with tabs and tabwidth=4, is
> better, but not much. Using tools like cat, less, diff (even svn
> diff), or a2ps is a pain because every line appears wrapped and is
> hard to read... (yes, I'm one of those old fools that refuse to live
> my life inside an IDE).
>
> But files with both indentation styles is, by far, the worst. I'm so
> tired of scanning my patches for places where I have accidently
> tab-indented a line in a method that's space-indented, or vice
> versa. This is perhaps not the most important issue in Derby, but I
> think it really cuts the "joy of development" factor for Derby. And
> that's not good for an open source project...
>
> --
> dt
>
>