Re: libstdc++/5133: Problems with toupper

[Pete Ratzlaff <rpete@legs.harvard.edu>]

The following reply was made to PR libstdc++/5133; it has been noted by GNATS.

From: Pete Ratzlaff <rpete@legs.harvard.edu>
To: Martin Sebor <sebor@roguewave.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/5133: Problems with toupper 
Date: Mon, 18 Nov 2002 00:50:16 -0500

 > > 
 > > I cannot see anything that keeps one from using the toupper/tolower
 > > from <cctype> with transform, and the fact that gcc won't allow it
 > > should be considered a bug.
 > 
 > Yes, but only if it's the only available function. The other comes
 > from <locale> which is probably indirectly #included by <iostream>.
 > 
 
 I had heard this argument before, for the case when both overloads from
 <locale> and <cctype> are in scope, but didn't know whether to believe
 it since no citations were ever shown. After digging around a bit (the
 template section of the standard is *dense*), I finally came across
 this:
 
 14.8.2.4
 
   16- A template-argument can be deduced from a pointer to function or
       pointer to member function argument if the set of overloaded
       functions does not contain function templates and at most one of a
       set of overloaded functions provides a unique match.
 
 So unless I'm misinterpretting, then your new explanation makes sense
 and gcc is conforming to the standard in this respect.
 
 Cheers,
 -Pete