Re: [Function] Implemented operator== and operator!=

<#part type="text/plain" filename="d:/TEMP/gcc_296_err.txt" disposition=attachment description="g++ 2.96 compiler output"> <#/part> User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (windows-nt) Cancel-Lock: sha1:mbn75GX0BrE0mKdP1bjMm9VxSrg= Douglas Gregor <gregod@cs.rpi.edu> writes:
On Tuesday 20 January 2004 01:29 pm, Douglas Gregor wrote:
On the main branch, I've implemented operator== and operator!= for Boost.Function (but not in the form you expect).
It's now documented.
I've also checked in some changes to handle reference_wrapper logically:
I just tried upgrading to the CVS mainline and got an internal compiler error in function_template.hpp when compiling one of the Python lib modules with gcc 2.96 linux. Reverting to RC_1_31_0 fixes the error. Recent lossage? /foo/boost/boost/python/errors.hpp:29: instantiated from `boost::python::handle_exception (T) [with T = void (*) ()]' /foo/boost/boost/python/errors.hpp:36: instantiated from here /foo/boost/boost/function/function_template.hpp:511: Internal error #373. /foo/boost/boost/function/function_template.hpp:511: confused by earlier errors, bailing out Compiler bug is documented at: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=57466 See attachment for more compiler output. -- Raoul Gough. export LESS='-X'

On Friday 30 January 2004 11:50 am, Raoul Gough wrote:
I just tried upgrading to the CVS mainline and got an internal compiler error in function_template.hpp when compiling one of the Python lib modules with gcc 2.96 linux. Reverting to RC_1_31_0 fixes the error. Recent lossage?
I don't have access to this compiler, so I can't test any fix. If you could play with it a bit to find a fix, I'll be happy to check it in. Doug
participants (2)
-
Douglas Gregor
-
Raoul Gough