------- Comment #2 from pinskia at gcc dot gnu dot org 2005-12-06 17:48 -------
No, GCC is correct to reject this code. What is happening is that the
overloaded set for the ChangeEndianness in the second ChangeEndianness is only
the first and the second so there is no way to consider the third (and the one
which you want) to be called.
This is the correct standards demanding behavior.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25278
