stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Sebor <se...@roguewave.com>
Subject Re: Internal Naming Conventions (Was RE: Compile-Time Integer Wrapper)
Date Wed, 14 May 2008 21:53:49 GMT
Eric Lemings wrote:
>  
> 
>> -----Original Message-----
>> From: Travis Vitek 
>> Sent: Wednesday, May 14, 2008 10:26 AM
>> To: Eric Lemings
>> Cc: Martin Sebor
>> Subject: RE: Compile-Time Integer Wrapper
>>
>>  
>>
>>> Eric Lemings wrote:
>>>
>>>
>>>> Travis Vitek wrote:
>>>>
> ...
>>>>     typedef _TypeT _C_value_type;
> ...
>>> What is the _C_ prefix supposed to indicate exactly?
>> Names that begin with an underscore followed by an uppercase 
>> letter or another underscore are reserved for the implementation.
> 
> Right.  That's specified in the standard.

The 'C' means Class member. We considered 'M' (for Member)
but that convention was already in use in at least two other
implementations.

> 
>> We typically use __rw_ to prefix for names of types in the 
>> __rw namespace. Local variables and parameters are usually 
>> prefixed with __, and member variables and typedefs usually 
>> get the _C_ prefix.
> 
> I assume you mean typedefs that are also members of a class.

Yes. There is no convention for local typedefs other than
that they match the "^_[A-Z]" RE.

Martin

> 
> So the _C_ prefix simply indicates that the name is internal member
> of a class?  Okay, just wanna make sure I have these (undocumented)
> naming conventions straight.  :)
> 
> Brad.


Mime
View raw message