This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 110c. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
[Voted into the WP at the February, 2012 meeting; moved to DR at the October, 2012 meeting.]
The current wording of 6.3 [basic.def.odr] paragraph 2 uses the term “overloaded” differently from its definition in Clause 12 [over] paragraph 1. For example, names found by argument-dependent lookup are not “overloaded” if they are not declared in the same scope. The phrasing should be reconciled between the two sections.
Proposed resolution (August, 2011):
Change 6.3 [basic.def.odr] paragraph 2 as follows:
non-overloadedfunction whose name appears as a potentially-evaluated expression or amember of a set of candidatefunctions , if selected by overload resolution when referred to from a potentially-evaluated expression, is odr-used, unless it is a pure virtual function and its name is not explicitly qualified...