[C++-sig] Re: method_call_expr not supported by dump_expr

[David Abrahams]

"Ralf W. Grosse-Kunstleve" <rwgk at yahoo.com> writes:

> --- David Abrahams <dave at boost-consulting.com> wrote:
>> "Marcelo A. Camelo" <camelo at esss.com.br> writes:
>> 
>> > Some further information:
>> >
>> > I've commented all my source code except 
>> > #include <boost/python.hpp>. The error persists.
>> >
>> > The error goes away when I use GCC 3.2.
>> >
>> > Can this be a GCC bug or a boost.Python non-conformance?
>> 
>> It's a GCC bug.  It's always possible that it was stimulated by a
>> Boost.Python non-conformance (though unlikely in this case), but that
>> "sorry, unimplemented" message is essentially an internal assertion
>> in the compiler.  Compilers should never do that.
>
> Romain's workaround solves this problem. Suggested patch attached. David, do
> you want this in CVS?
>
> Index: as_to_python_function.hpp
> ===================================================================
> RCS file:
> /cvsroot/boost/boost/boost/python/converter/as_to_python_function.hpp,v
> retrieving revision 1.1
> diff -u -r1.1 as_to_python_function.hpp
> --- as_to_python_function.hpp   2 Dec 2002 01:37:39 -0000       1.1
> +++ as_to_python_function.hpp   22 May 2003 16:29:14 -0000
> @@ -27,6 +27,9 @@
>      {
>          BOOST_STATIC_ASSERT(
>              sizeof(
> +#if defined(__GNUC__) && __GNUC__ == 3 && __GNUC_MINOR__ == 3 &&
> __GNU_PATCHLEVEL__ == 0
> +                as_to_python_function::
> +#endif

Yes, please.  I sent a different simple suggestion in response to your
"Mac OS 10 success" message which I'd like you to quickly try first.
If it doesn't work out, please go ahead with the above patch.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com