No, not a single IDE. That's like ordering a single size of boots for an army. I was thinking
along the lines of a Pretty Printer.
> -----Original Message-----
> From: Jason Dillon [mailto:jason@coredevelopers.net]
> Sent: Wednesday, August 13, 2003 9:33 AM
> To: geronimo-dev@incubator.apache.org
> Subject: Re: Suggested coding convention: sort methods
>
>
> Single tool? Like a single IDE? Not gonna happen IMO.
>
> --jason
>
>
> On Wednesday, August 13, 2003, at 08:28 PM,
> <Dirk.Weibel@ferguson.com>
> wrote:
>
> > I'm also 1+ on consistant coding standards/conventions, regardless
> > what form they take. Maybe I'm missing something, but what's the
> > difference between automatically enforcing style and manually
> > refactoring a class to be in conformance with the standard? Would
> > standardizing on a single tool resolve the sync problem?
> >
> >> -----Original Message-----
> >> From: Mark Mahieu [mailto:mark@twistedbanana.demon.co.uk]
> >> Sent: Wednesday, August 13, 2003 9:13 AM
> >> To: geronimo-dev@incubator.apache.org
> >> Subject: Re: Suggested coding convention: sort methods
> >>
> >>
> >> The real can of worms is opened when developers start
> >> reformatting code
> >> with Pretty Printers or IDEs and then try to get their
> >> patches applied;
> >> everything is suddenly out of sync with what's in CVS. Even
> >> automatically enforcing the style as it gets checked in
> >> doesn't really
> >> avoid that one.
> >>
> >> I'm sure I could find some earlier, er, 'discussions' about
> >> this in the
> >> archives of other mailing lists for everyone's amusement ;-)
> >>
> >> For what it's worth, I'm +1 on the general idea though.
> >>
> >> Mark
> >>
> >>
> >
>
>
|