[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Code formatting standards?

From: McClain Looney <mlooney_at_gmail.com>
Date: 2004-09-25 02:12:46 CEST

I agree, the formatting is a mess.

Unfortunately, as I've learned from hard experience, a wholesale
reformatting of a codebase causes massive pain down the road. History
basically starts and ends the day that commit is made, since literally
hundreds of meaningless diffs will be caused in the history of every
source file.

That, and eclipse doesn't provide an easy way of associating a format
convention on a per-project basis. subclipse may want it one way, but
cruisecontrol wants their code another way and so on, ad infinitum.

despite the objections noted above, i'll be saying 0 to this if it
ever comes up for a vote. i've been dealing with hideous code too long
to be bothered by it now.

ps. please direct queries of this nature to dev@subclipse.tigris.org

----- Original Message -----
From: Robert Simmons <kraythe@arcor.de>
Date: Sat, 25 Sep 2004 00:49:01 +0200
Subject: Code formatting standards?
To: users@subclipse.tigris.org

 

 

I was looking at the code for the decorators and the formatting makes
one wince. Is there a set of standard settings for the subclipse
project? If not Id like to suggest some. The prefs file is attached.
All code should be formatted to the same standard. It's a pain to read
5 different coding styles all the time.

  

  

-- Robert Simmons Jr.

-- Senior Software Architect, Consultant

  

Author of "Hardcore Java", Published by O'Reilly, ISBN: 0-596-00568-7,
http://www.oreilly.com/catalog/hardcorejv

  

 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org

-- 
McClain Looney
m@loonsoft.com
Received on Sat Sep 25 10:12:46 2004

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.