Proposed resolution (February, 2010):

1. Change the index to refer to “implicit object parameter” and “implied object argument” instead of the current permutations of these terms.

2. Change 12.2 [over.match] paragraph 1 as follows:

...how well (for non-static member functions) the object matches the implied implicit object parameter...

3. Change 12.2.2 [over.match.funcs] paragraph 4 as follows:

...For conversion functions, the function is considered to be a member of the class of the implicit implied object argument for the purpose of defining the type of the implicit object parameter...

4. Change the footnote in 12.2.4 [over.match.best] bullet 1.1 as follows:

• [Footnote: If a function is a static member function, this definition means that the first argument, the implied object parameter argument, has no effect in the determination of whether the function is better or worse than any other function. —end footnote]

The terminology used to refer to the parameter for this and its corresponding argument is inconsistent, sometimes using “implied” and sometimes “implicit.” It would be easier to search the text of the Standard if this usage were made regular.

History Date User Action Args 2010-03-29 00:00:00adminsetmessages: + msg2723 2010-03-29 00:00:00adminsetstatus: tentatively ready -> cd2 2010-02-16 00:00:00adminsetmessages: + msg2506 2009-11-20 00:00:00admincreate