[Bug c++/22206] New: gcc overload resolution fails to follow "using" in some cases

[Bug c++/22206] New: gcc overload resolution fails to follow "using" in some cases

[kjd at duda dot org]

gcc-3.4.3 fails to accept this valid program:

namespace Fwk {
  int valueToStrep( char const * ) { return 100;}
}
using Fwk::valueToStrep;
namespace Foo {
  int valueToStrep( int ) { return 200; }
  int foo2() { return valueToStrep( "hello" ); }
}

If you comment out the second "valueToStrep" function (the one that returns
200), then the program compiles as expected.

If you add a "using Fwk::valueToStrep" to "namespace Foo", then the program
compiles as expected.

This may be related to bug 20724.

Thanks,
    -Ken

-- 
           Summary: gcc overload resolution fails to follow "using" in some
                    cases
           Product: gcc
           Version: 3.4.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: kjd at duda dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i386-redhat-linux
  GCC host triplet: i386-redhat-linux
GCC target triplet: i386-redhat-linux


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

[Bug c++/22206] gcc overload resolution fails to follow "using" in some cases

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2005-06-27 23:07 -------
This is invalid code but I don't have the time to explain why except to say that when inside a 
namespace, you look into the inner most namespace first and if it does not find any then the outer for 
overloads.

-- 


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

[Bug c++/22206] gcc overload resolution fails to follow "using" in some cases

[bangerth at dealii dot org]

------- Additional Comments From bangerth at dealii dot org  2005-06-28 13:57 -------
Andrew is correct: name lookup proceeds from the present scope outward and 
stops once it finds a matching name (note: name, not signature) or names. It 
then tries to match the signature of the names to the call. This fails here. 
There is no requirement that the compiler then resume looking for other names 
in scopes further out. 
 
W. 

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


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