[Bug c++/38005] inconsistent precedence of operators in namespaces

[c dot hite at rtsgroup dot net]

------- Comment #5 from c dot hite at rtsgroup dot net  2008-11-04 10:47 -------
I'm fine with case #1.  I don't know if Sun is wrong, or there is no "right".

#2 is a BUG.

No, the lookup doesn't stop at "operator<<(Thing&o,Thing&)", it keeps going,
but it keeps going differently.

Please look at it.  In namespace C after the compiler realizes that the local
operator doesn't match, I expect it to try the other operators in the same
order as if that local operator didn't exist.

Why do C and D generate different calls?  When deciding between the other two
operators outside their namespace C and D should reach the same decision.


-- 

c dot hite at rtsgroup dot net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38005