commit-classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Patch: FYI: hacking update


From: Tom Tromey
Subject: Patch: FYI: hacking update
Date: 02 Apr 2004 14:20:08 -0700

I'm checking this in.  This documents a couple more redundant bits
that we can omit in our coding standard.

Let me know if you object to this change; I'm assuming everybody will
pretty much find it unobjectionable, but if I'm wrong I will back it
out.

Tom

Index: ChangeLog
from  Tom Tromey  <address@hidden>
        * doc/hacking.texinfo (Source Code Style Guide): Mention `extends
        Object' and `import java.lang.Integer' as redundant.

Index: doc/hacking.texinfo
===================================================================
RCS file: /cvsroot/classpath/classpath/doc/hacking.texinfo,v
retrieving revision 1.24
diff -u -r1.24 hacking.texinfo
--- doc/hacking.texinfo 2 Apr 2004 16:23:13 -0000 1.24
+++ doc/hacking.texinfo 2 Apr 2004 21:31:55 -0000
@@ -585,22 +585,23 @@
 @end example
 
 @item
-Don't use redundant modifiers.  Here is some sample code that shows
-redundant modifiers in comments:
+Don't use redundant modifiers or other redundant constructs.  Here is
+some sample code that shows various redundant items in comments:
 
 @example
+/*import java.lang.Integer;*/
 /*abstract*/ interface I @{
    /*public abstract*/ void m();
    /*public static final*/ int i = 1;
    /*public static*/ class Inner @address@hidden
 @}
-final class C @{
+final class C /*extends Object*/ @{
    /*final*/ void m() @address@hidden
 @}
 @end example
 
-Note that Jikes will generate warnings for these if you use
address@hidden on the command line.
+Note that Jikes will generate warnings for redundant modifiers if you
+use @code{+Predundant-modifiers} on the command line.
 
 @item
 Modifiers should be listed in the standard order recommended by the




reply via email to

[Prev in Thread] Current Thread [Next in Thread]