Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Rajiv Gupta <rajiv@invalid.com>
Newsgroups: comp.lang.java.programmer
Subject: Re: Style Police (a rant)
Date: Sat, 27 Aug 2011 18:02:17 +1000
Organization: Aioe.org NNTP Server
Lines: 15
Message-ID: <j3a8a7$7h5$1@speranza.aioe.org>
References: <j39fdc$1hi$1@dont-email.me>
NNTP-Posting-Host: QXLpeSPZoolsWYKJ4tlfjg.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Complaints-To: abuse@aioe.org
User-Agent: Unison/2.1
X-Notice: Filtered by postfilter v. 0.8.2
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:7409

On 2011-08-27 10:56:40 +1000, Eric Sosman said:
> 
>     I wonder what this Checkstyle tool would think of the concrete,
> non-final, non-empty equals(), hashCode(), clone(), toString(), and
> finalize() methods of ... java.lang.Object, the one class *no* Java
> program can avoid extending.  If java.lang.Object is "not designed for
> extension," is there any hope left for the language?
> 
>      Enforcing good style is difficult.  I wish the purveyors of the
> enforcement tools would realize it's beyond their powers to do it well.

You are not forced to use the tool.  These tool are often written by 
the pedants and those who don't have much real world experience.   The 
correctness checking inbuilt into modern IDEs is sufficient anyway.