This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Partial ordering bug (?) in egcs


>>>>> "Thomas" == Thomas Kunert <kunert@physik.tu-dresden.de> writes:


    Thomas> an exact match for `IndexPlaceholder<N_index>'. I see some
    Thomas> advantages in my interpretation: 
    Thomas> + some useful constructs are supported (e.g. Todd's
    Thomas> example) 
    Thomas> + it's portabel :-)

There is one major disadvantage, though; it's not how the language
works.  :-(

    Thomas> Are there examples that wouldn't work with my point of
    Thomas> view?

Of course; if you were to allow this kind of thing you would change
the way overload resolution behaves.  In Todd's example, you would
remove an ambiguity, but in others you might equally well add one.

-- 
Mark Mitchell 			mark@markmitchell.com
Mark Mitchell Consulting	http://www.markmitchell.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]