Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Andreas Leitgeb <avl@logic.at>
Newsgroups: comp.lang.java.programmer
Subject: Re: Uppercase methods names
Date: Wed, 1 Feb 2017 01:07:33 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 17
Message-ID: <slrno92d9s.pvm.avl@logic.at>
References: <namens-20170131023341@ram.dialup.fu-berlin.de>
Reply-To: avl@logic.at
Injection-Date: Wed, 1 Feb 2017 01:07:33 -0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="8cd7e2f23cfeda94ac98302d7b731d7e"; logging-data="4294"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+rA0sCmMnWN43BBXO1hEnN"
User-Agent: slrn/1.0.2 (Linux)
Cancel-Lock: sha1:wwlITKmgAAD6yX+limDjrHcy2L4=
Xref: csiph.com comp.lang.java.programmer:36238

Stefan Ram <ram@zedat.fu-berlin.de> wrote:
>   This is not mentioned in JLS 6.1, but are
> public static int java.awt.Color.HSBtoRGB(float,float,float)
> [...]
>   enough prior art to derive a rule:

Reminds me of a similar "problem" for Java beans, and their properties:

A JMS-related bean-class has method setSSLCipherSuite(...), and I just played
try&error to see if the property would start with "SSL", "sSL" or "ssl".
Iirc it was "SSL".

PS: proper study of bean-ology or the net might have saved me from try&error
and surprises, but merely adding that one property to an existing xml didn't
make it feel worth yet to dig into it any deeper. I was already happy to find
the method name on the net.