This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/6532: STL binder1st::operator() not compiling
- From: Olaf Dietsche <olaf dot dietsche at gmx dot net>
- To: paolo at gcc dot gnu dot org
- Cc: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
- Date: Thu, 02 May 2002 11:54:50 +0200
- Subject: Re: libstdc++/6532: STL binder1st::operator() not compiling
- References: <20020501170044.28756.qmail@sources.redhat.com>
Hi Paolo,
thanks for your fast response.
paolo@gcc.gnu.org writes:
> Synopsis: STL binder1st::operator() not compiling
>
> Responsible-Changed-From-To: unassigned->paolo
> Responsible-Changed-By: paolo
> Responsible-Changed-When: Wed May 1 10:00:42 2002
> Responsible-Changed-Why:
> Triaged.
> State-Changed-From-To: open->closed
> State-Changed-By: paolo
> State-Changed-When: Wed May 1 10:00:42 2002
> State-Changed-Why:
> Duplicate of libstd++/5012: not a bug, but instead standard conforming behaviour.
I've taken a look at this bug report. So, the library is implemented
conforming to the C++ Standard, but unfortunately the issue
remains.
How am I supposed to use this binder/mem_fun combination for modifying
methods? Changing the signature to call by value is not an option
here, since the semantics would be changed too.
This seems like a bug or at least an oversight in the standard. What
am I missing?
Thanks for your time.
Regards, Olaf.