Title
Global namespace scope
Status
tc1
Section
10.3 [basic.namespace]
Submitter
Greg Lutz

Created on 1999-09-19.00:00:00 last changed 208 months ago

Messages

Date: 1999-10-15.00:00:00

Proposed resolution (10/00):

  1. Replace the first sentence of 6.3.6 [basic.scope.namespace] paragraph 3 with

    The outermost declarative region of a translation unit is also a namespace, called the global namespace. A name declared in the global namespace has global namespace scope (also called global scope).
  2. In the last sentence of the same paragraph, change "Names declared in the global namespace scope" to "Names with global namespace scope."

  3. Replace 10.3 [basic.namespace] paragraph 2 with

    The outermost declarative region of a translation unit is a namespace; see 6.3.6 [basic.scope.namespace].

Date: 2003-04-25.00:00:00

10.3 [basic.namespace] paragraph 2 says:

A name declared outside all named namespaces, blocks (9.3 [stmt.block] ) and classes (clause 12 [class] ) has global namespace scope (6.3.6 [basic.scope.namespace] ).
But 6.3.6 [basic.scope.namespace] paragraph 3 says:
A name declared outside all named or unnamed namespaces (10.3 [basic.namespace] ), blocks (9.3 [stmt.block] ), function declarations (11.3.5 [dcl.fct] ), function definitions (11.4 [dcl.fct.def] ) and classes (clause 12 [class] ) has global namespace scope (also called global scope).
10.3 [basic.namespace] should evidently be changed to match the wording in 6.3.6 [basic.scope.namespace] — the unnamed namespace is not global scope.
History
Date User Action Args
2003-04-25 00:00:00adminsetstatus: dr -> tc1
2000-11-18 00:00:00adminsetstatus: ready -> dr
2000-05-21 00:00:00adminsetstatus: review -> ready
2000-02-23 00:00:00adminsetmessages: + msg221
1999-09-19 00:00:00admincreate