This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: shadowed rel_ops operators
- To: libstdc++ at gcc dot gnu dot org
- Subject: Re: shadowed rel_ops operators
- From: Nathan Myers <ncm at nospam dot cantrip dot org>
- Date: Sun, 21 Jan 2001 11:24:41 -0800
- References: <0C79E524ECB8D311BB48009027765E8A0B74BA@BASKETBALL>
- Reply-To: libstdc++ at gcc dot gnu dot org
On Sun, Jan 21, 2001 at 12:38:14PM +1100, Richard Andrews wrote:
> From: Nathan Myers
> > Yes. It is not the iterator operators that break rel_ops, but rather
> > the rel_ops operators that break the iterator operators, as indeed they
> > break all similar operators.
> >
> > The rel_ops operators are not useful. They were a mistake. If you
> > insist on using them, you will have trouble. Nobody will care, because
> > you asked for it.
>
> OK. It sounds like the rel_ops operators were a mistake to include in the
> standard. So are there any plans to remove them from the standard?
Unfortunately not.
> What will be the standing of libstdc++ if rel_ops breaks libstdc++ or
> vice-verse? Is this a problem with other implementations of C++?
Since nobody can implement template comparison operators that are
compatible with the rel_ops templates, it's the same everywhere.
The right thing to do is to put a prominent comment in the rel_ops
header warning about it. Probably an FAQ item would be good too.
Nathan Myers
ncm at cantrip dot org