I don't think you meant camel case -- but Title Case. This would be
camelCase.


Cheers,
Paul


On Mon, May 19, 2014 at 8:31 AM, Matt Sicker <[email protected]> wrote:

> There's only one type of acceptable all-caps class name: URL/URI and the
> like. I do indeed prefer CamelClassFactoryUrlBuilders myself.
>
>
> On 19 May 2014 06:35, Gary Gregory <[email protected]> wrote:
>
>> We use Camel Case even for acronyms at work. SOAPHTTPRPCListener? Bleh!
>>
>> Gary
>>
>>
>> -------- Original message --------
>> From: Remko Popma
>> Date:05/19/2014 04:19 (GMT-05:00)
>> To: Log4J Developers List
>> Subject: Re: Guidelines
>>
>> That must have been a lot of work. Thanks for putting that together!
>>
>> I think the current version of the guidelines still has "no wildcart
>> imports" as a rule. We may want to change that pending our discussion on
>> the other thread.
>>
>> Also interesting that Google recommends to use CamelCase for acronyms (so
>> they prefer XmlHttpConverter to XMLHTTPCOnverter).
>>
>> Otherwise I think we're pretty much in line already.
>>
>> Again, thanks!
>> Remko
>>
>> Sent from my iPhone
>>
>> > On 2014/05/19, at 13:46, Ralph Goers <[email protected]>
>> wrote:
>> >
>> > I have added the nosql and web projects to the site build and excluded
>> the bom project from it.
>> >
>> > I added a first version of project guidelines and style guidelines.
>> Both should be considered preliminary at this point and as a starting point
>> for discussion - not a final result, although they should be considered to
>> be in effect once the next release is cut and the site is published.
>> >
>> > The project guidelines were borrowed from the HTTPD project and edited
>> to be specific to Log4j. I also added the guidelines I suggested on the
>> list a few weeks ago.
>> >
>> > As for the style guidelines, I borrowed Google’s since I can’t seem to
>> find the Sun guidelines. Oracle seems to have deleted them or moved them
>> somewhere google doesn’t know about.  I modified some of the guidelines to
>> match things I know we do differently but kept most of them.  They are
>> probably incomplete and some may need to be changed.
>> >
>> > Ralph
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected]
>> > For additional commands, e-mail: [email protected]
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
> --
> Matt Sicker <[email protected]>
>

Reply via email to