search for: ismyconditiontrue

On Oct 13, 2014, at 3:44 PM, Chandler Carruth <chandlerc at google.com> wrote: > I actually have a particular allergy to member variable names and function names having similar styles: > > bool x = i->isMyConditionTrue; > > Did I mean to write 'isMyConditionTrue()'? Or 'bool &x = I->isMyConditionTrue'? Or something else? I have no idea. Warnings and other things can help reduce the likelihood of this becoming a live bug, but it still makes the code harder to read IMO. This is exactl...

...apple.com> wrote: > >> On Oct 13, 2014, at 3:44 PM, Chandler Carruth <chandlerc at google.com> >> wrote: >> > I actually have a particular allergy to member variable names and >> function names having similar styles: >> > >> > bool x = i->isMyConditionTrue; >> > >> > Did I mean to write 'isMyConditionTrue()'? Or 'bool &x = >> I->isMyConditionTrue'? Or something else? I have no idea. Warnings and >> other things can help reduce the likelihood of this becoming a live bug, >> but it still makes...

> If we are going to change how we name variables, I very much want them to > not collide with either type names or function names. My suggestion would be > "lower_case" names. > > This also happens to be the vastly most common pattern across all C++ coding > styles and C-based language coding styles I have seen. STL has "lower_case" functions, and exposes

...ct 13, 2014, at 3:44 PM, Chandler Carruth <chandlerc at google.com> >>>> wrote: >>>> > I actually have a particular allergy to member variable names and >>>> function names having similar styles: >>>> > >>>> > bool x = i->isMyConditionTrue; >>>> > >>>> > Did I mean to write 'isMyConditionTrue()'? Or 'bool &x = >>>> I->isMyConditionTrue'? Or something else? I have no idea. Warnings and >>>> other things can help reduce the likelihood of this becoming a live b...