Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!.POSTED!not-for-mail From: Lew Newsgroups: comp.lang.java.programmer Subject: Re: Curious compiler warning Date: Thu, 12 Jan 2012 07:55:39 -0800 Organization: albasani.net Lines: 35 Message-ID: References: <9n64rgF40bU1@mid.individual.net> <1igsg7d3eggiptf23g9vd0flv19ghqs83d@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.albasani.net g038nC9a9nju97ch5kN1rrdz0W97KEanI6hG4XzGTIrdCbuN2H/XSBJ2EI2T16dEGo40+FB4c11U5MhUYcWNzxIZAdPyKvoGRLX4duw8apKnaVHyjkd8/7k8ybK8SicF NNTP-Posting-Date: Thu, 12 Jan 2012 15:55:37 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="CA06rbJUf49W+FK2vrxiKl+p3rMVDzJv/RWUK1s2FmjLUx9JQOtlpU+egM+we33zEV+0CP44v/1Hv+Cw24jbanIIPh/k2V/rOC4zVH1mVorgSZl1AzGtFtus/7rHcCIl"; mail-complaints-to="abuse@albasani.net" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Thunderbird/3.1.16 In-Reply-To: <1igsg7d3eggiptf23g9vd0flv19ghqs83d@4ax.com> Cancel-Lock: sha1:0bl+YVJWLiERzJnzFcRqKGl2lcI= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:11269 On 01/11/2012 06:18 PM, Gene Wirchenko wrote: > Oh, my. Bad style. That is bad, isn't it? I am wearing a dark > grey sweater and medium brown pants. Is anyone's compiler concerned > about my style? > > "style" and "best practices" get bandied about as if they are > sacred. Often, they are merely someone's opinion, and not necessarily > a well-thought-out one either. > > If a parameter is call-by-value, it is available for modification > in many languages. Such code is shorter, too. I prefer a concise > style. Except perhaps for auto-inc/decrement and op-assignment? When the pundits call these things "bad style", it's completely unrelated to matters of personal taste. You are stalking a dead horse. They have engineering reasons, in the case of the OP's complaint a perceived risk of error from the idiom. It is the presence of such risk that makes the style "bad". If you can objectively prove such risk exists, the style is bad. If you can objectively prove it does not, the style is good. If you don't know, you can claim one or the other as an hypothesis but not a theory. So everyone who wants to minimize the risk of error in a program cares about your style, and you should, too! People should feel free to write compilers that support such criteria. Oh, hey! Eclipse did! And the issues that are not proven to be bad style, but claimed by enough wise people to be, are *options* to enforce in that compiler. Dju better get chyo style toGETHah, yo! -- Lew Honi soit qui mal y pense. http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg