search for: humblecamelcase

FWIW, I'm pretty strongly opposed to humbleCamelCase. We already use that style so something else. One of the biggest advantages of changing the variable naming convention would be to differentiate variables from other constructs IMO, and that's the nature of many examples here. Using underscore_names for variables as Zach suggests would,, onhe...

...oesn't make sense to do a purely aesthetic move that not everyone is going to agree on anyway, when we could do one with actual tangible value. On Wed, Feb 13, 2019 at 8:52 AM <paul.robinson at sony.com> wrote: > Chandler wrote: > > > FWIW, I'm pretty strongly opposed to humbleCamelCase. We already use that > > style so something else. > > Presumably you are equally opposed to RegularCamelCase, because we already > use *that* style for something else. > > But really, objecting on the grounds that a given style is already used for > function names is really...

...ot everyone is >> going to agree on anyway, when we could do one with actual tangible value. >> >> On Wed, Feb 13, 2019 at 8:52 AM <paul.robinson at sony.com> wrote: >> >>> Chandler wrote: >>> >>> > FWIW, I'm pretty strongly opposed to humbleCamelCase. We already use >>> that >>> > style so something else. >>> >>> Presumably you are equally opposed to RegularCamelCase, because we >>> already >>> use *that* style for something else. >>> >>> But really, objecting on the gro...

It very much depends on what is following the code snippit. If the second "if" is guarding a substantial block of code, "constantExpr" might very well be a good name. Otherwise something like "cExpr" or "constExpr" might be fine. In the past when I have seen things like "CE" in the code, it's not always immediately clear to me what it is. I