mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny" <elecha...@gmail.com>
Subject Re: Coding stlye guide
Date Wed, 16 May 2007 18:38:28 GMT
The link I have posted contains pointers to such files, btw.

Emmanuel

On 5/16/07, Mark Webb <elihusmails@gmail.com> wrote:
>
> There is a way to import these rules as an xml file into Eclipse.  Not
> sure
> what everyones IDE of choice is, but I would bet that other IDE's have the
> same functionality.
>
> So should we develop a standard and then set up the configuration for
> different development environments?
>
> --
> ..Cheers
> Mark
>
> On 5/16/07, Mladen Turk <mturk@apache.org> wrote:
> >
> > Hi,
> >
> > Looking at MINA sources I found out that the coding style is
> > different from what I'm used to. Well, it's personal anyhow, but
> > it should be important.
> >
> > Are there any rules for that?
> > I have noticed few:
> >
> > 1. After each '(' there must be a space.
> >     Exception is if next char is ')'
> > 2. There must be a space before ')' except for #1
> > 3. There must be a space after ')' unless it's a last char
> > 4. Curly braces must be on the new line below the statement
> > 5. Use spaces instead tabs
> > 6. Use 4 spaces idents
> > 7. Remove trailing spaces
> > 8. Each for/if/else/try/catch/do/while block must have
> >     curly braces even for a single statement.
> >
> > It would be great if there is some .indent file because
> > I already noticed that there are some files that are
> > starting to break those rules.
> >
> > Regards,
> > Mladen.
> >
> >
>



-- 
Regards,
Cordialement,
Emmanuel L├ęcharny
www.iktek.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message