Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!74.125.46.80.MISMATCH!postnews.google.com!news2.google.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!spln!extra.newsguy.com!newsp.newsguy.com!news3 From: Wojtek Newsgroups: comp.lang.java.programmer Subject: Re: Call by Result Date: Tue, 14 Jun 2011 00:40:27 -0700 Organization: NewsGuy - Unlimited Usenet $19.95 Lines: 49 Message-ID: References: <4DF2289B.5030909@NnOwSlPiAnMk.com> <56q4v6h1afrmkktk7rqiolgdqqkms387tv@4ax.com> NNTP-Posting-Host: p9edd8edad2b688fd756ccbaa04342ea98b3377de48e32d3a.newsdawg.com Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15"; format=flowed Content-Transfer-Encoding: 8bit X-Newsreader: MesNews/1.08.03.00-gb Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5295 Gene Wirchenko wrote : > On Sat, 11 Jun 2011 16:35:03 -0700, Wojtek wrote: > Yup. Why have a bunch of different formats for what is about the > same thing? Hmm, this statement has a slight disconnect with this statement: > Could be. I will follow such conventions as have been set. > My code is not obfuscated. Sometimes, I am the one setting the > standard by right of being the only progammer. If not, I ask for the > standards and then follow them. If you are the originator of a language then you can set whatever standards (um, conventions) you want. And others will follow them to keep consistent with you. But if you are coding in a generally used language then it behooves you to follow the generally accepted conventions. To do otherwise will confuse some future maintenance programmer and will also present your work as amateurish. Visual Basic by convention capitalizes function names. Java by convention does not. And K&R C and PHP do not use camel case. VB: public function DoMyWork() as String Java: public string doMyWork() C: char* do_my_work() PHP: function do_my_work() I find all of these readable, however I would NEVER mix the different ways of naming a method. There is one thing that has pretty well been consistent over the years. ALL the code I have ever written HAS been looked at by someone else, no matter how off-the-cuff and temporary I thought it was when I wrote it. And since I have had many juniors working for me, it is my responsibility to teach them the accepted way of presenting code in whatever language I happen to be using at the time. No matter how much they think it is not necessary. A convention is just that. A generally accepted way of doing things. -- Wojtek :-)