Paul,
I have installed the Checkstyle plug-in for Eclipse and I will be
giving it a spin with the XML file you provided.
Thanks,
The Sunburned Surveyor
On 6/1/07, Paul Austin <[EMAIL PROTECTED]> wrote:
> The Eclipses checkstyle plugin comes with the config for the Sun
> conventions, which I hav
01, 2007 8:07 AM
> > To: List for discussion of JPP development and use.
> > Subject: Re: [JPP-Devel] Code Style Standards
> >
> >
> > Paul,
> >
> > Please see my comments below.
> >
> > Paul wrote: "I think a good set of standards to follow are
&g
Friday, June 01, 2007 8:07 AM
> To: List for discussion of JPP development and use.
> Subject: Re: [JPP-Devel] Code Style Standards
>
>
> Paul,
>
> Please see my comments below.
>
> Paul wrote: "I think a good set of standards to follow are
> the Sun Java Code
The Eclipses checkstyle plugin comes with the config for the Sun
conventions, which I have attached to this email.
I recommend that you get the Eclipse plugin
http://eclipse-cs.sourceforge.net/ and then set enable this for a
project to check that you want to use all those rules (some of them y
Paul,
Please see my comments below.
Paul wrote: "I think a good set of standards to follow are the Sun Java Code
Conventions. It's a fairly short (ish) standard and avoids all the
variable prefix and class prefix stuff.
http://java.sun.com/docs/codeconv/CodeConventions.pdf";
I agree with you. T
I think a good set of standards to follow are the Sun Java Code
Conventions. It's a fairly short (ish) standard and avoids all the
variable prefix and class prefix stuff.
http://java.sun.com/docs/codeconv/CodeConventions.pdf
In terms of package imports I don't ever manually type imports any more
Martin,
Please see my comments below.
Martin wrote: "Well, now we're getting closer to the bone... As tools
have improved
I've found myself using name prefixes in fewer and fewer situations.
All the IDEs I've used in the last 6 yrs can easily tell you whether
something is a class or an interface
Rant on Martin.
LOL
Larry
On 5/29/07, Martin Davis <[EMAIL PROTECTED]> wrote:
>
>
> Sunburned Surveyor wrote:
> > Martin,
> >
> > See my comments below.
> >
> > Martin wrote: "Naming of
> > methods, classes and packages is more visible (in increasing importance)
> > - articulating some policies h
Sunburned Surveyor wrote:
> Martin,
>
> See my comments below.
>
> Martin wrote: "Naming of
> methods, classes and packages is more visible (in increasing importance)
> - articulating some policies here might be helpful."
>
> You make a good point here. I prefix all of my interfaces with a
> capi
Martin,
See my comments below.
Martin wrote: "Naming of
methods, classes and packages is more visible (in increasing importance)
- articulating some policies here might be helpful."
You make a good point here. I prefix all of my interfaces with a
capital "I", all of my exceptions with the prefix
Here's my 2c worth.
I agree that we shouldn't reqire a standard which is onerous for
developers that aren't using a particular IDE.
I also agree that the curly brace position issue is not worth wasting
time over. Much better to spend the time doing better Javadoc.
Variable naming is also pr
One of the topics discussed in an earlier thread today was code format
standards or code style standards.Using tools that will allow us to
automatically enforce a coding standard was suggested. Using these
tools to convert existing source code from other JUMP "brands" to our
style for OpenJUMP was
12 matches
Mail list logo
