why no ambiguity error in code?

Hello everyone,


Any ideas why there is no ambiguity issues in the code? Which myfunc is called?

The code can pass compile and link in Visual Studio 2008 without any warning messages. The output is 100.

Code:

---

int myfunc (int& a) {return 100;}

int myfunc (const int& a) {return 200;}

int main()
{
        int a = 1;
        int& ra = a;
        int rtn;
        rtn = myfunc (ra); // call which myfunc? output 100
        return 0;
}

---

thanks in advance,
George

My deduction is that it uses the non-const version, because ra is not a const. Try using a const int &cra and call myfunc(cra) and see if that doesn't return 200.

--
Mats

int& is an exact match. const int& would have to add a const. Clearly, int& is the better match and is thus used.

Thanks CornedBee,


But if we remove & and change code to the following segment,

Code:

---


int myfunc (int a) {return 100;}

int myfunc (const int a) {return 200;}

---

There will be duplicated defined function error. So I think the rules are,

1. (as you said) compiler allow more than one matched function exist, but has a priority to match them;
2. (as I showed above) for const reference and non-const reference, compiler will treat them of two different functions, but for non-const value and const value, compiler will treat them as same functions.

My conclusions (1) and (2) are correct?

Quote:

---

Originally Posted by CornedBee

int& is an exact match. const int& would have to add a const. Clearly, int& is the better match and is thus used.

---

regards,
George

1) Correct.
2) Also correct. And if you'll refer back to your recent overriding thread, I said there quite explicitly that top-level cv qualifiers don't matter in function resolution. int and const int are treated the same. int& and const int& are not, because the const is not top-level.

Thanks CornedBee,


Question answered.

Quote:

---

Originally Posted by CornedBee

1) Correct.
2) Also correct. And if you'll refer back to your recent overriding thread, I said there quite explicitly that top-level cv qualifiers don't matter in function resolution. int and const int are treated the same. int& and const int& are not, because the const is not top-level.

---

regards,
George