------- Additional Comments From rwgk at yahoo dot com  2005-01-06 19:51 -------
Date: Thu, 06 Jan 2005 14:24:06 -0500
From: David Abrahams

Ralf W. Grosse-Kunstleve wrote:
> Hi David,
> 
> To ensure that Boost.Python will work with gcc 4 I've checked out the
> latest gcc cvs today, along with the latest boost cvs. There are lots
> of errors when compiling the Boost.Python tests, but as far as I can
> tell only two types of errors. One is an internal compiler error, i.e.
> there is no question that I have to file a bug report for this one.
> However, I am not sure about the second one. Could you please have a
> look?
> 
>   Raw error message:
>     http://cci.lbl.gov/~rwgk/bugs/gcc_cvs_head_20050106/error_which_is_of_non_
class_type
> 
>   Same but processed with gSTLFilt.pl:
>     http://cci.lbl.gov/~rwgk/bugs/gcc_cvs_head_20050106/error_which_is_of_non_
class_type_stlfilt

That's not much help, is it!?

> If you think it is a gcc 4 problem rather than a boost problem
> I'll file a bug report.

Well, let's see.  I think you can do this analysis yourself, FWIW:

/net/legless/scratch1/rwgk/hot/boost/boost/python/object/make_instance.hpp:63:
error: request for member M-CM-"M-bM-^BM-,M-KM-^\get_class_objectM-CM-"M-bM-^B
M-,M-bM-^DM-" in
M-CM-"M-bM-^BM-,M-KM-^\boost::python::converter::detail::registered_base<const v
olatile
Y&>::convertersM-CM-"M-bM-^BM-,M-bM-^DM-", which is of non-class type M-CM-"M-b
M-^BM-,M-KM-^\const
boost::python::converter::registration&M-CM-"M-bM-^BM-,M-bM-^DM-"

It seems to be claiming that the static

   registration const&

member named "converters" of

  registered_base<Y const volatile&>

Doesn't have class type.  Clearly wrong.  I mean, it's a reference to an
object of class type, but for all purposes other than initialization you
can do the same things with that as you can do with a class instance.

> Thanks!
>         Ralf
> 
> BTW: Do you know what to make of the strange characters (e.g. M-CM-"M-bM-^BM-,
M-bM-^DM-")?

GCC bug?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19298

Reply via email to