db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manish Khettry <manish_khet...@yahoo.com>
Subject Re: [VOTE] Approve coding conventions for the Derby project
Date Sat, 12 Aug 2006 00:21:43 GMT
+1

I see that we're deferring tabs vs spaces and the "{"
position issue for later.

--- Andrew McIntyre <mcintyre.a@gmail.com> wrote:

> On 8/11/06, Kathey Marsden
> <kmarsdenderby@sbcglobal.net> wrote:
> > This is a vote to define the coding conventions
> for the Derby project
> > per the db project guidelines
> http://db.apache.org/source.html
> > Vote closes  10:00am, Wednesday, August  15.
> >
> > [+1]  Adopt the coding convention described.
> > [-1 ] Do not adopt the coding convention
> described.
> >
> > The conventions outlined below will be published
> on the wiki page
> >
>
http://wiki.apache.org/db-derby/DerbyContributorChecklist
> >
> > Derby uses the "Code Conventions for the Java
> Programming Language"
> >
>
(http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html)
> with these
> > amendments:
> >  - space indentation (no tabs).
> >  - Derby does not discourage deferring variable
> declaration to the first
> > use.
> >  - Lines should be limited to 80 characters
> >  - @author tags should not be used at all
> >
> > Note: There is a great deal of existing code that
> does not match this
> > convention. Changes to existing code should match
> the surrounding code
> > for readability, matching tabs or spaces as
> appropriate (see Tabs) .
> > Patches should not have white space diffs. Code
> and diffs should be
> > readable in  context.
> 
> +1
> 
> andrew
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Mime
View raw message