search for: metasyntactic

...d (abbreviation and non-descriptive); might be 829 // OK for a local variable if its role is obvious. I'll reword the rule to match what you have in mind. > For capitalization, I generally prefer capital names with the exception being one character names that are often metasyntactic names (like 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 vari...

...you have in mind. I've made the change and uploaded the new patch to http://codereview.appspot.com/3264041 -- you can also find it attached to this message. Thanks, > >> For capitalization, I generally prefer capital names with the exception being one character names that are often metasyntactic names (like 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. > >...

Zhanyong Wan (λx.x x) wrote: > 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 Typ...

...blems with macros (e.g. system headers that define things like "i386") but there are straight-forward ways to deal with this. There is no need to live life in fear :) >> For capitalization, I generally prefer capital names with the exception being one character names that are often metasyntactic names (like 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. Yes, I...

On Sun, Nov 28, 2010 at 11:02 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> I enjoyed the new coding style in recent patches. Camel case makes it easy >> to pick a descriptive name. Starting functions and variables with lower >> cases reduces chances to conflict with a type name. > Honestly speaking, I don't. Especially in the cases when varname is

...made the change and uploaded the new patch to > http://codereview.appspot.com/3264041 -- you can also find it attached > to this message. Thanks, > > > > >> For capitalization, I generally prefer capital names with the exception > being one character names that are often metasyntactic names (like 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...