MESSAGE
| DATE | 2011-06-05 |
| FROM | Ruben Safir
|
| SUBJECT | Subject: [NYLXS - HANGOUT] (fwd) Re: Anonymous namespace
|
-- forwarded message --
Path: reader1.panix.com!panix!bloom-beacon.mit.edu!micro-heart-of-gold.mit.edu!nntp.club.cc.cmu.edu!feeder.erje.net!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Ian Collins
Newsgroups: comp.lang.c++
Subject: Re: Anonymous namespace
Date: Sat, 04 Jun 2011 17:31:37 +1200
Lines: 29
Message-ID: <94tu9qFivcU5-at-mid.individual.net>
References: <94rjavFbjiU7-at-mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net ZwlZUHupngJ/lBraN7J8tQLIAnXFbv+s9wnDz4z3XI+8qPIgKs
Cancel-Lock: sha1:nbiUB89B74iEea7DRPunWPp7lgo=
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.9) Gecko/20101021 Lightning/1.0b2 Thunderbird/3.1.4
In-Reply-To:
Xref: panix comp.lang.c++:1086011
On 06/ 4/11 05:05 PM, Ruben Safir wrote:
> On Fri, 03 Jun 2011 20:12:15 +1200, Ian Collins wrote:
>
>>
>>>
>>> please expand?
>>
>> One way to look at the anonymous namespace is to consider it a namespace
>> with a cryptic name. That name is only known within the current
>> compilation unit. Thus anything declared within the namespace can't
>> been seen elsewhere because the namespace name is unknown.
>>
>> So I could write
>>
>> namespace { int n; }
>>
>> and n would only be visible within the current compilation unit whereas
>>
>> int n;
>>
>> would be globally visible.
>
> Ok - I'm getting a clearer picture. What specifically did you mean,
> however, by the phrase "even if they should have external linkage"
Not declared static.
--
Ian Collins
-- end of forwarded message --
|
|
