Re: coding style: to camel or not

2009-12-10 Thread John Plevyak
Regarding the m_ for member, I agree that for private/protected variables an indicator is a good idea. Regular members are always accessed by reference outside the object, so it seems obvious that it is a member: cache_read_vio->nbytes is a member and it doesn't help (me) to have it be: cach

Re: coding style: to camel or not

2009-12-10 Thread Paul Querna
On Thu, Dec 10, 2009 at 10:44 AM, Manjesh Nilange wrote: >> MACROS >> ClassNames >> memberFunctions >> members_variables > > How about having an 'm_' prefix to distinguish member variables from > local variables? I know this is a couple of more characters to type, but > I find it nicer to be able

RE: coding style: to camel or not

2009-12-10 Thread Manjesh Nilange
> MACROS > ClassNames > memberFunctions > members_variables How about having an 'm_' prefix to distinguish member variables from local variables? I know this is a couple of more characters to type, but I find it nicer to be able to distinguish class member variables easily. The rest of the list lo