[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Classpath Swing development?
From: |
Thomas Zander |
Subject: |
Re: Classpath Swing development? |
Date: |
Mon, 24 May 2004 22:40:28 +0200 |
User-agent: |
KMail/1.6.2 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Since you asked :)
On Monday 24 May 2004 20:30, Andrew John Hughes wrote:
> If there are issues not covered here, you should
> raise them on the list so they can be added.
What is missing is a guide or download that makes it possible for JAVA
programmers to start hacking. As soon as gcc, automake and autoconf come
into play you loose 75% of your potential hackers-market for any Java
project.
A snapshot with generated makefiles, and an included libtool would be a
very good start.
On the hacking guide point 6.1, for the following item;
Don't use redundant modifiers or other redundant constructs. Here is some
sample code that shows various redundant items in comments:
/*import java.lang.Integer;*/
/*abstract*/ interface I {
/*public abstract*/ void m();
/*public static final*/ int i = 1;
/*public static*/ class Inner {}
}
final class C /*extends Object*/ {
/*final*/ void m() {}
}
The one who wrote this obviously has no idea that
public void bla()
is very different from
void bla()
and
class x{ int i=1; }
is very different from:
class x{ public static final int i=1; }
an inner class is also not static by default.
An additional item for the coding style should be a note that if you
implement equals() then you should also implement hashCode();
What I also miss is the ordering inside a class; what I see most of the
java community do is to put static fields first, then normal fields, then
constructors, then private/protected constructors, then public get/set
style methods, then normal public methods, then private methods, then all
static methods, then non-static inner classes, then static inner classes.
This is what the industry uses; I don't really care what the standard is in
GNU classpath, but I surely would like to see a coding convention.
- --
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAsl28CojCW6H2z/QRAq2sAKDA9o5XxvcWKyZL75h/iEyRKh+K+gCgy3nv
d1r4k5oNuXkNDYWpyMVtCvg=
=4gQo
-----END PGP SIGNATURE-----
- Re: Classpath Swing development?, (continued)
- Re: Classpath Swing development?, Roman Kennke, 2004/05/24
- Re: Classpath Swing development?, Mark Wielaard, 2004/05/24
- Re: Classpath Swing development?, Stephen Crawley, 2004/05/24
- Re: Classpath Swing development?, Valentin Chira, 2004/05/25
- Re: Classpath Swing development?, Tom Tromey, 2004/05/25
- Re: Classpath Swing development?, Roman Kennke, 2004/05/25
- Re: Classpath Swing development?, Dalibor Topic, 2004/05/26
- Re: Classpath Swing development?, John Leuner, 2004/05/25
- Re: Classpath Swing development?, Thomas Zander, 2004/05/25
- Re: Classpath Swing development?, Tom Tromey, 2004/05/25
- Re: Classpath Swing development?,
Thomas Zander <=
- Re: Classpath Swing development?, Dalibor Topic, 2004/05/25
- Re: Classpath Swing development?, Tom Tromey, 2004/05/25
Re: Classpath Swing development?, Tom Tromey, 2004/05/24
Re: Classpath Swing development?, Roman Kennke, 2004/05/24