Path: csiph.com!aioe.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk>
Newsgroups: comp.lang.java.programmer
Subject: Re: Pascal case of the field "BidiElementName"
Date: Wed, 22 Mar 2017 19:45:40 -0400
Organization: Aioe.org NNTP Server
Lines: 30
Message-ID: <oav2b2$1reo$1@gioia.aioe.org>
References: <Pascal-20170301030546@ram.dialup.fu-berlin.de> <oaubt1$bst$1@gioia.aioe.org>
NNTP-Posting-Host: PBuS014lhzVyHjLbXmo/ZQ.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:36418

On 3/22/2017 1:22 PM, Tristan B. Kildaire wrote:
> On 2017-03-01 04:08 AM, Stefan Ram wrote:
>>   Why are most of the field names of the type
>>
>> javax.swing.text.AbstractDocument
>>
>>   written in Pascal case?
>>
>>   »BidiElementName«, »ContentElementName« ,
>>   »ElementNameAttribute«, ...
>>
> Camel case?

Pascal case is XxxxXxxxXxxx.

Camel case at least when compared to pascal case is xxxxXxxxXxxx.

Java convention is pascal case for type names and camel case
for member names.

Which is probably why Stefan asked.

But some of those were static final also known as const
so they should really have been all uppercase with underscore
aka XXXX_XXXX_XXXX.

https://en.wikipedia.org/wiki/PascalCase

Arne