Re: [boost] Re: Small thing: yes_type and no_type made public?

From: David Abrahams (dave_at_[hidden])
Date: 2003-01-08 15:45:45

"Paul Mensonides" <pmenso57_at_[hidden]> writes:

> ----- Original Message -----
> From: "David Abrahams" <dave_at_[hidden]>
> To: "Boost mailing list" <boost_at_[hidden]>
> Sent: Wednesday, January 08, 2003 12:14 PM
> Subject: Re: [boost] Re: Small thing: yes_type and no_type made public?
>
>
>> hartmutkaiser_at_[hidden] (Hartmut Kaiser) writes:
>>
>> >
>> > //  The following expands to
>> > //
>> > // typedef char (&sizeN_t)[N];
>> > //
>> > //  for N = 1..BOOST_MAX_SIZETYPE_COUNT
>> > #define SIZETYPE(z, n, nil) \
>> > typedef char (&size ## n ## _t)[n]; \
>> > /**/
>>
>> Careful; isn't the symbol "_t" reserved to the implementation in this
> context?
>
> I thought it was only if the underscore was followed by a capital letter, as
> in "_T".

    17.4.3.1.2 Global names
    1 Certain sets of names and function signatures are always reserved to
    the implementation:

    --- Each name that contains a double underscore (_ _) or begins with
    an underscore followed by an upper- case letter (2.11) is reserved to
    the implementation for any use.

    --- Each name that begins with an underscore is reserved to the
    implementation for use as a name in the global namespace. 165)

I guess the global namespace doesn't apply to macros, huh ;-)

-- 
                       David Abrahams
   dave_at_[hidden] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution