Why a new source formatter in M4? [message #104729] |
Tue, 14 October 2003 19:11  |
Eclipse User |
|
|
|
Originally posted by: derisor.arcor.de
From:
http://download2.eclipse.org/downloads/drops/S-3.0M4-2003101 01454/eclipse-news-part1-M4.html
The new Java code formatter can be enabled via the Java > Work in Progress >
Code Formatter preference page. This formatter will be much more flexible than
its predecessors, although you'll have to take that on faith until its new
preference page is ready.
I am curious why they are bothering re-implementing this when there are already
a couple of formatters available and, in fact, potentially the best formatter
ever, Jalopy. Wouldn't it make more sense to try to integrate Jalopy more
tightly into Eclipse and build on their successes?
-- Kraythe
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Why a new source formatter in M4? [message #107779 is a reply to message #107765] |
Mon, 20 October 2003 04:08   |
Eclipse User |
|
|
|
Thorsten Schäfer wrote:
>
> Robert Simmons" wrote:
>> This is a very bad idea in corporate development... >8
>> Spending time to figure out someones style leads to wasted time... >8
>> It is far better to describe company wide formatting standards
>> and enforce them rigorously.
>
> Why? The proposed solution results in one corporate coding standard
> which is persisted in the CVS. But in addition to that, every
> developer has the possibility to view the source like he wants to. I
> think standardization is a good thing, if it doesn't hurt the users.
> Enforcement of a single coding standard is always hard...
Here, here! Additionally, from the perspective of someone who's
employed contractors, and who's done a little contracting:
(a) Contract developers don't necessarily know, or agree with, or want
to pollute their minds with, a particular company's coding styles, so
this will be a very popular feature with such individuals.
(b) From the employer's perspective, when paying a contractor by the
day, they want to avoid learning curves, eliminating the need to impart
and enforce a coding style saves money and will therefore be popular at
a corporate level.
This, of course, does not negate anything Robert says about the benefit
that the company gains from having a single corporate coding style,
which I agree is most important, but it does save money and make the
development task easier - which is what an IDE is about.
Now; what about C, COBOL, etc? I do hope the mechanism will work for
any code in any repository.
Rich
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.12384 seconds