This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: something wrong with template instantiation mechanics
- To: kriol at fnal dot gov (Oleg Krivosheev), egcs at cygnus dot com
- Subject: Re: something wrong with template instantiation mechanics
- From: Jason Merrill <jason at cygnus dot com>
- Date: 10 Oct 1997 11:43:31 -0700
- References: <Pine.GSO.3.96.971009221207.6871A-100000@drabble><Pine.GSO.3.96.971009232426.6908A-100000.cygnus.egcs@drabble>
>>>>> Oleg Krivosheev <kriol@fnal.gov> writes:
> after reading CD2 and thinking a bit i still
> believe this is a bug:
> 14.8.3 Overload resolution [temp.over]
> ..
> For each function template, if the argument
> deduction succeeds, the deduced template-arguments are used to instan-
> tiate a single function template specialization which is added to the
> candidate functions set to be used in overload resolution.
> ..
> well, lloks like egcs deduces templates argument right,
Yes.
> then it properly did everload resolution and
> choose template version of abs
No. It chose the non-template abs declared by the line
friend numT abs( const TVector3D<numT>& );
Jason