> > Besides, why the profusion of operator == and
> operator !=? Isn't it
> > enough with one of them?
>
> There's a Standard C++ Library header that generates some operator
> overloads in terms of others, but I can't remember the name.
> Anway, it's
> almost certainly not available on all platforms.
In the <utility> header I believe. Given operator== and operator<, you get
all other relational operators for free. But ... they are defined in
namespace std::rel_ops and as you may recall, namespaces are on the list of
language features that xercesc avoids.
> >Well, even without that, a != b is exactly the same as !( a == b ) ...
> To be sure... Perhaps, perhaps not. Depends what operator!=
> and operator==
> are defined to be.
Even _if_ the expressions mean the same thing, it isn't very polite to force
your users to write quirky things like that when you easily can hide it in
the library. In other words, it makes client code a lot clearer and avoids
programmer frustration.
cheers,
Pieter
**** DISCLAIMER ****
"This e-mail and any attachments thereto may contain information which is
confidential and/or protected by intellectual property rights and are
intended for the sole use of the recipient(s) named above.
Any use of the information contained herein (including, but not limited to,
total or partial reproduction, communication or distribution in any form) by
persons other than the designated recipient(s) is prohibited.
If you have received this e-mail in error, please notify the sender either
by telephone or by e-mail and delete the material from any computer.
Thank you for your cooperation."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
