Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: Designation of a non-static method Date: Thu, 20 Dec 2012 13:47:04 -0800 Organization: Canadian Mind Products Lines: 15 Message-ID: References: Reply-To: Roedy Green NNTP-Posting-Host: K2Qzzs3EAqXk5RLzfhxcSw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: csiph.com comp.lang.java.programmer:20647 On 20 Dec 2012 19:06:03 GMT, ram@zedat.fu-berlin.de (Stefan Ram) wrote, quoted or indirectly quoted someone who said : > I used to think that it was common usage to use »C.f()« for > a static method »f()« and »C#f()« for a non-static method > »f()« of a class »C«. Random.nextDouble will not compile, but that is how the method is named in JavaDoc. I suppose JavaDoc could be changed to generate random.nextDouble to hint at the instanceness. On the other hand, you will get a warning if you do someobject.somestatic(). -- Roedy Green Canadian Mind Products http://mindprod.com Students who hire or con others to do their homework are as foolish as couch potatoes who hire others to go to the gym for them.