...@gmail.com> writes: Can someone explain this peculiar behavior of MSVC & GCC: Yes. NB: Your question isn't related to argument dependant (aka Koenig) lookup. It's a basic overloading problem (if these exist at all). code below, if you uncomment that line (which is totally unrelated to '...

Thomas Maeder wrote: void AAA::dph::f() { std::cout << *this; This statement causes the compiler to look for operator<<()s in a sequence of scopes. The first scope considered is the struct dph, which doesn't have an operator<<() member. Minor correction, woldn't actually look it up in std::cout's as a member and not in struct dph? (since dph is a second ...

On May 6, 10:24 am, Michael Kilburn <crusader.m...@gmail.com> wrote: Hi Can someone explain this peculiar behavior of MSVC & GCC: code below, if you uncomment that line (which is totally unrelated to 'dph' class), will stop compiling with usual bizzare C++ error [code] #include <iostream> namespace AAA { struct gad { }; //std::...

Michael Kilburn wrote: Hi Can someone explain this peculiar behavior of MSVC & GCC: code below, if you uncomment that line (which is totally unrelated to 'dph' class), will stop compiling with usual bizzare C++ error [code] #include <iostream> namespace AAA { struct gad { }; //std::ostream& operator<<(std::ostream& s, gad const&); ...

Hi Can someone explain this peculiar behavior of MSVC & GCC: code below, if you uncomment that line (which is totally unrelated to 'dph' class), will stop compiling with usual bizzare C++ error [code] #include <iostream> namespace AAA { struct gad { }; //std::ostream& operator<<(std::ostream& s, gad const&); struct dph { void f();...