From: Olaf Petzold <opetzold@wit.regiocom.net>
To: GCC Mailing List <gcc@gcc.gnu.org>
Subject: stl_relops.h collision conflict
Date: Tue, 11 Sep 2001 04:57:00 -0000 [thread overview]
Message-ID: <01091113315100.02113@gatekeeper> (raw)
Hello,
I'm writing an ET library. Unfortunally I'm gone into trouble
with the stl internal header stl_relops.h from gcc:
template <class _Tp>
inline bool operator>(const _Tp& __x, const _Tp& __y) {
return __y < __x;
}
and my:
template<class T1, class T2, size_t Sz>
inline
Xpr<
XprBinOp<
VectorReference<T1, Sz>,
Functional::Greater<T1, T2>,
VectorReference<T2, Sz>
>
>
operator>(const Vector<T1, Sz>& lhs, const Vector<T2, Sz>& rhs) {
typedef XprBinOp<
VectorReference<T1, Sz>,
Functional::Greater<T1, T2>,
VectorReference<T2, Sz>
> expr_type;
return Xpr<expr_type>(expr_type(lhs.ref(), rhs.ref()));
}
Is there no way to force the compiler to use my implementation of
operator>() ?
On gcc-3.0.1 the relops header has an own inner namespace but, the problems
has been occoured in prior version as well. Is there a work around ?
Thanks
Olaf
next reply other threads:[~2001-09-11 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 4:57 Olaf Petzold [this message]
2001-09-11 10:26 ` Joe Buck
2001-09-12 2:42 ` Olaf Petzold
2001-09-12 12:50 ` Joe Buck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01091113315100.02113@gatekeeper \
--to=opetzold@wit.regiocom.net \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).