Section: 188.8.131.52 [global.functions] Status: TC1 Submitter: Lois Goldthwaite Opened: 1999-06-04 Last modified: 2016-02-10
Priority: Not Prioritized
View all other issues in [global.functions].
View all issues with TC1 status.
The library had many global functions until 184.108.40.206 [lib.contents] paragraph 2 was added:
All library entities except macros, operator new and operator delete are defined within the namespace std or namespaces nested within namespace std.
It appears "global function" was never updated in the following:
220.127.116.11 - Global functions [lib.global.functions]
-1- It is unspecified whether any global functions in the C++ Standard Library are defined as inline (dcl.fct.spec).
-2- A call to a global function signature described in Clauses lib.language.support through lib.input.output behaves the same as if the implementation declares no additional global function signatures.*
[Footnote: A valid C++ program always calls the expected library global function. An implementation may also define additional global functions that would otherwise not be called by a valid C++ program. --- end footnote]
-3- A global function cannot be declared by the implementation as taking additional default arguments.
18.104.22.168 - Member functions [lib.member.functions]
-2- An implementation can declare additional non-virtual member function signatures within a class:
-- by adding arguments with default values to a member function signature; The same latitude does not extend to the implementation of virtual or global functions, however.
Change "global" to "global or non-member" in:
22.214.171.124 [lib.global.functions] section title,
126.96.36.199 [lib.global.functions] para 1,
188.8.131.52 [lib.global.functions] para 2 in 2 places plus 2 places in the footnote,
184.108.40.206 [lib.global.functions] para 3,
220.127.116.11 [lib.member.functions] para 2
Because operator new and delete are global, the proposed resolution was changed from "non-member" to "global or non-member.