search for: uppercamelcase

TL;DR: change the rule for variable names from UpperCamelCase to lowerCamelCase. Just to get wider visibility on this, I'm raising this again as an RFC, as suggested by Roman Lebedev. My original post from last week is here and gives a rationale: http://lists.llvm.org/pipermail/llvm-dev/2019-February/129854.html. There seemed to be general agreement t...

...<dexonsmith at apple.com> wrote: >> I argue we should spell C++ lambdas (and other function-like variables) like functions, not like variables. >> >> - Use verbs, not nouns. > > I think I agree with this. > >> - Use lowerCamelCase. > > In lld we use UpperCamelCase, as they are technically not function names but variable names. Using lowerCamelCase for function pointers feels really weird to me, as they are really variables than functions to me. I also agree that this is weird either way because they are variables when declared and passed around and function...

...gt;> I argue we should spell C++ lambdas (and other function-like variables) like functions, not like variables. > >> > >> - Use verbs, not nouns. > > > > I think I agree with this. > > > >> - Use lowerCamelCase. > > > > In lld we use UpperCamelCase, as they are technically not function names but variable names. Using lowerCamelCase for function pointers feels really weird to me, as they are really variables than functions to me. > > I also agree that this is weird either way because they are variables when declared and passed around an...

...llvm.org> On Behalf Of Michael Platings via llvm-dev > Sent: den 7 februari 2019 23:11 > To: llvm-dev at lists.llvm.org > Cc: nd <nd at arm.com> > Subject: [llvm-dev] RFC: changing variable naming rules in LLVM codebase > > TL;DR: change the rule for variable names from UpperCamelCase to lowerCamelCase. > > > > Just to get wider visibility on this, I'm raising this again as an RFC, as suggested by Roman Lebedev. > > > > My original post from last week is here and gives a rationale: http://lists.llvm.org/pipermail/llvm-dev/2019-February/129854....

...latings via llvm-dev >>> Sent: den 7 februari 2019 23:11 >>> To: llvm-dev at lists.llvm.org >>> Cc: nd <nd at arm.com> >>> Subject: [llvm-dev] RFC: changing variable naming rules in LLVM codebase >>> TL;DR: change the rule for variable names from UpperCamelCase to >>> lowerCamelCase. >>> >>> >>> >>> Just to get wider visibility on this, I'm raising this again as an RFC, as suggested by Roman Lebedev. >>> >>> >>> >>> My original post from last week is here and gives...

I argue we should spell C++ lambdas (and other function-like variables) like functions, not like variables. - Use verbs, not nouns. - Use lowerCamelCase. Here's a patch that implements the change to the coding standards: https://reviews.llvm.org/D48991 <https://reviews.llvm.org/D48991> Thoughts? -------------- next part -------------- An HTML attachment was scrubbed... URL:

...but not optimal according to most common needs, that are 1. Name a package 2. Name a class 3. Name a function 4. Name a parameter of a function 5. Name a variable My approach is the following 1. Package names should be made of lowercase characters, dash, dot and underscore 2. Class names are UpperCamelCased 3. Function names are lowerCamelCased 4. Function parameters are semantic names resulting from underscore separated lowerCamelCased function name, type acronym and length specification. 5. Variable should be snake case That way you can not confuse one for the other. This brings clear view, ea...

> On Feb 12, 2019, at 4:02 AM, Björn Pettersson A via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > (Sorry if this subject already has been discussed, but I could not find any clear rules/recommendations.) > > What would the recommendation be for acronyms (I’ve seen the rule about avoiding them unless they are “well known”, > but sometimes an acronym is useful, and we

...februari 2019 23:11 >> >>> To: llvm-dev at lists.llvm.org >> >>> Cc: nd <nd at arm.com> >> >>> Subject: [llvm-dev] RFC: changing variable naming rules in LLVM >> codebase >> >>> TL;DR: change the rule for variable names from UpperCamelCase to >> >>> lowerCamelCase. >> >>> >> >>> >> >>> >> >>> Just to get wider visibility on this, I'm raising this again as an >> RFC, as suggested by Roman Lebedev. >> >>> >> >>> >> &...

Won't it be better to have a convention that allows lowercase, dash, underscore and dot as only valid characters for new package names and keep the ancient format validation scheme for older package names? This could be implemented by a single function, taking a strictNaming_b_1 parameter which defaults to true. Easy to use, and compliance results will vary according to the parameter value,