Hi, On Fri, 2006-01-06 at 07:21 +1100, Raif S. Naffah wrote: > On Friday 06 January 2006 06:45, Casey Marshall wrote: > > Of course, a lot of GNU Crypto's source is formatted in a completely > > non-standard way: the file opens with the 'package' line, then the > > copyright boilerplate (with // comments), then the class. And, the > > source is formatted with non-GNU style indentation, and an indent > > length of 3. I remember seeing code reformatters mentioned here > > before; will they work here? Is it worth reformatting all this code? > > Tom Tromey, some time ago, worked on Jalopy, to customize it to suit GNU > formatting standard purposes. he may be able to shed some light on the > tool's fitness for this purpose. if it works that can solve this issue > --and a similar one in the Mauve part for the corresponding testlets.
There is also the eclipse formatter. Ben Konrath has packaged this as standalone tool http://www.bagu.org/eclipse/efj/ especially for use by GNU Classpath hackers. > > This will probably happen after 0.20. OK. Lets not stress about getting evertyhing cleaned/cleared up before that then. Thanks, Mark -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Classpath-patches mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath-patches
