On Tue, 11 Feb 2003, Konstantin Piroumian wrote:

> From: "Vadim Gritsenko" <[EMAIL PROTECTED]>
> > Pier Fumagalli wrote:
> >
> > >As in every project where a bunch of people are contributing at the same
> > >time, one day or another, it comes up "what kind" of coding style one
> > >actually want to have throughout the source code...
> > >
> > >I was wondering if there are some guidelines for Cocoon (back in the days
> > >when I started there weren't, but maybe now)...
> > >
> > >Personally I use "checkstyle" at work (I actually enforced it over there
> to
> > >have a consistent coding style) and it works all right.
> > ><http://checkstyle.sf.net>
> > >
> > >Our coding properties for verification are pretty basic:
> > >
> > >  checkstyle.maxlinelen=120
> > >  checkstyle.ignore.braces=true
> > >
> > >And instinctively I adopted them also for the HttpProxyGenerator. I was
> > >wondering if it's allright for the others and whether it adheres to the
> > >current ones or not (I wasn't able to figure out if there was a coding
> > >convention throughout the sources)...
> > >
> > >What do you guys think?
> > >
> >
> > I'd like to see 4-spaces-indent, max line length somewhere in 80-100
> > diapason, and the rest does not matter match... You can take (almost)
> > any core class as an example (say, Cocoon.java ;).
>
> I am used to the Sun's coding standarts. I have the Guidelines for it on my
> HDD, but don't remember where I got them. They basically state:
>     - 4 space indent
>     - Kernighan-Ritchi style braces (no new line before opening brace):
>         function Name() {
>             //
>         }
>     - 80 character line length (but I think that 17" displays are quite
> common now and the limit can be extended to 120)
>     - variableName - lower case variable names
>     - ClassName - upper case class names
>
> and a lot of other things.
> You'll find the document here:
> http://cvs.apache.org/~kpiroumian/gdl_sun_java_style.pdf

I currently using JIndent(http://www.jindent.com/), so I wrote
an jindent format file for most used coding style. It works quite well. If
any interest exist I can put it into the repository.

Stephan Michels.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to