hello all, On Friday 06 January 2006 20:01, Mark Wielaard wrote: > 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...
i tried it and it does re-format the source --i used the eclipse-gnu.xml specs included in the GNU Classpath scripts folder. it does not however fix the copyright block, which i think Jalopy was/is able to do as well. cheers; rsn
pgpCiRdYSpgjU.pgp
Description: PGP signature
_______________________________________________ Classpath-patches mailing list [email protected] http://lists.gnu.org/mailman/listinfo/classpath-patches
