Displaying 4 results from an estimated 4 matches for "strictcamelcase".
2010 Nov 23
6
[LLVMdev] draft rule for naming types/functions/variables
...ike i/j).
If possible, I'd prefer that all variable names have the same style.
I'm afraid that we'll end up with the current inconsistent style if we
leave it to people to interpret whether a name is metasyntactic and
thus should be lower-case.
Also, having both types and variables in StrictCamelCase increases the
chance of clashing between the two and thus sometimes makes it hard to
choose good variable names. For example, if you have a function that
takes a Type parameter, how would you name the parameter if it has to
start with an upper-case? There are several obvious choices:
void Visi...
2010 Nov 23
0
[LLVMdev] [cfe-dev] draft rule for naming types/functions/variables
...;d prefer that all variable names have the same style.
> I'm afraid that we'll end up with the current inconsistent style if
> we
> leave it to people to interpret whether a name is metasyntactic and
> thus should be lower-case.
>
> Also, having both types and variables in StrictCamelCase increases
> the
> chance of clashing between the two and thus sometimes makes it hard
> to
> choose good variable names. For example, if you have a function
> that
> takes a Type parameter, how would you name the parameter if it has
> to
> start with an upper-case? There a...
2010 Nov 23
0
[LLVMdev] draft rule for naming types/functions/variables
...I'd prefer that all variable names have the same style.
> I'm afraid that we'll end up with the current inconsistent style if we
> leave it to people to interpret whether a name is metasyntactic and
> thus should be lower-case.
>
> Also, having both types and variables in StrictCamelCase increases the
> chance of clashing between the two and thus sometimes makes it hard to
> choose good variable names. For example, if you have a function that
> takes a Type parameter, how would you name the parameter if it has to
> start with an upper-case? There are several obvious c...
2010 Nov 29
8
[LLVMdev] draft rule for naming types/functions/variables
...ariable names have the same style.
> > I'm afraid that we'll end up with the current inconsistent style if we
> > leave it to people to interpret whether a name is metasyntactic and
> > thus should be lower-case.
> >
> > Also, having both types and variables in StrictCamelCase increases the
> > chance of clashing between the two and thus sometimes makes it hard to
> > choose good variable names. For example, if you have a function that
> > takes a Type parameter, how would you name the parameter if it has to
> > start with an upper-case? There a...