Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #36233
| From | Eric Sosman <esosman@comcast-dot-net.invalid> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Uppercase methods names |
| Date | 2017-01-31 08:14 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <o6q2h0$clu$1@dont-email.me> (permalink) |
| References | <namens-20170131023341@ram.dialup.fu-berlin.de> |
On 1/30/2017 8:36 PM, Stefan Ram wrote:
> This is not mentioned in JLS 6.1, but are
>
> public static int java.awt.Color.HSBtoRGB(float,float,float)
> public static double java.lang.Math.IEEEremainder(double,double)
> public static float[] java.awt.Color.RGBtoHSB(int,int,int,float[])
> public static long java.util.Date.UTC(int,int,int,int,int,int)
> public static native double java.lang.StrictMath.IEEEremainder(double,double)
>
> enough prior art to derive a rule:
>
> »When a method name starts with an acronym that usually
> is written in all-upperase, it is still written in
> all-uppercase when it appears at the start of a method
> name«?
Why bother deriving a RULE!!! from the names of a mere six
methods, one of them deprecated?
(I suppose there's precedent for RULE!!!-making on tiny
samples. Long years ago I was required to memorize a RULE!!!
concerning Latin semi-deponent verbs whose direct objects took
the ablative rather than the accusative case; there were five
count them five such verbs. I still feel that making a RULE!!!
in such cases is sub-optimal; call 'em "irregular" and move on.)
--
esosman@comcast-dot-net.invalid
Fourteen hundred fifty days to go.
Back to comp.lang.java.programmer | Previous | Next — Next in thread | Find similar | Unroll thread
Re: Uppercase methods names Eric Sosman <esosman@comcast-dot-net.invalid> - 2017-01-31 08:14 -0500 Re: Uppercase methods names Eric Douglas <e.d.programmer@gmail.com> - 2017-01-31 06:02 -0800 Re: Uppercase methods names Eric Sosman <esosman@comcast-dot-net.invalid> - 2017-01-31 12:40 -0500
csiph-web