Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #20647 > unrolled thread

Re: Designation of a non-static method

Started byRoedy Green <see_website@mindprod.com.invalid>
First post2012-12-20 13:47 -0800
Last post2012-12-20 13:47 -0800
Articles 1 — 1 participant

Back to article view | Back to comp.lang.java.programmer

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Designation of a non-static method Roedy Green <see_website@mindprod.com.invalid> - 2012-12-20 13:47 -0800

#20647 — Re: Designation of a non-static method

FromRoedy Green <see_website@mindprod.com.invalid>
Date2012-12-20 13:47 -0800
SubjectRe: Designation of a non-static method
Message-ID<fj17d8tn3qqb9fsob2k6sn3vvmo9kkgrhu@4ax.com>
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. 

[toc] | [standalone]


Back to top | Article view | comp.lang.java.programmer


csiph-web