Displaying 3 results from an estimated 3 matches for "lowercaseletterthencamelcase".
2019 Feb 04
2
Variable names rule
I so agree. I have found scope based coding conventions very useful. My favorite was:
* Static data member: s_<lowerCaseLetterThenCamelCase>
* Non-static data members: _<lowerCaseLetterThenCamelCase> (This was allowed by the C++ standard I last read. It’s _<UpperCase> that is reserved)
* Function argments: <lowerCaseLetterThenCamelCase>_
* Function local...
2019 Feb 03
4
Variable names rule
> On Feb 2, 2019, at 8:18 PM, Chris Lattner <clattner at nondot.org> wrote:
>
>
>
>> On Feb 1, 2019, at 6:20 AM, Michael Platings via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>>
>> Hi all,
>>
>> As application of the naming rules are currently under discussion [1] this seems like a good time
2019 Feb 04
2
Variable names rule
...<Michael.Platings at arm.com>; llvm-dev <llvm-dev at lists.llvm.org>; nd <nd at arm.com>
Subject: Re: [llvm-dev] Variable names rule
On Mon, 4 Feb 2019 at 17:20, JD Jones via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> · Non-static data members: _<lowerCaseLetterThenCamelCase> (This was allowed by the C++ standard I last read. It’s _<UpperCase> that is reserved)
This is about the one thing I'd be truly unhappy to see us adopt (for any situation). I think the interaction with acronyms is just too pathological. You get a really weird identifier or UB, possib...