ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <stev...@iseran.com>
Subject Re: [Suggestion][New Task] Coding Standards / Code 'Beautifier'
Date Wed, 17 Jan 2001 22:50:48 GMT
I've used the java style thingy in jedit. try it to see if you like it.

-it applies the layout and bracked position policies of your choosing
(good)
-it fills out the doc comments with parameter and exception values
(good)

-it sorts around where functions go
(bad)

-it added an extra line feed between every line in my dos file
(v.bad, even though the build still worked)

If the latter bug gets fixed (maybe already) then it would be a nice tool.
Dunno if I'd include it in a build file though; the editor is close enough.
But having it as an ant task could be useful in some cases.

-steve

----- Original Message -----
From: "Preston L. Bannister" <preston@home.com>
To: <ant-dev@jakarta.apache.org>
Sent: Wednesday, January 17, 2001 11:36 AM
Subject: RE: [Suggestion][New Task] Coding Standards / Code 'Beautifier'


> From: Martin van den Bemt [mailto:mvdb@mvdb.com]
> > So this functionality could be a (cvs) commit processing rule, a
extension
> > to current development environments or a nice task in Ant, but not core
to
> > Ant.
>
> I'd put this a bit more strongly.
>
> This topic has come up before, elsewhere BTW.
>
> If the re-format gets *anything* wrong you can break code.
>
> So the sequence should be:
>
>   * reformat
>   * build
>   * run all tests
>   * cvs checkin
>
> Assuming that the tests are complete...
>
> It is at least doubtful that you want this to be an
> automatic process.
>
> --
> Preston L. Bannister
> preston@home.com
> http://members.home.com/preston/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: ant-dev-help@jakarta.apache.org
>
>


Mime
View raw message