From: Allen Yao (yaozhen_at_[hidden])
Date: 2004-05-23 20:14:37
I fixed bugs in serialization18 yesterday.
The bugs are almost all about dependent names:
- lacking "this->" before "This()", "base_reference()", "newtoken()",
and some data members inherited from templated base class.
(BTW: using -fpermissive cannot fix the bugs about dependent data members.)
I cannot find why the following cannot compile using GCC 3.4:
basic_oarchive & ar,
const void * t,
const basic_oserializer_pointer & bos_ptr
ar << class_name_type(key); // This line causes an error message said that
// boost::noncopyable's ctor is
I am eager to see Ramey's post-review version of the Serialization Library,
for I am using
the library in my current project.
"Robert Ramey" <ramey_at_[hidden]> ????
> Allen Yao wrote:
> > I just updated my gcc from 3.3.3 to 3.4, and found that the
> > serialization17 and serialization18 cannot compile. There are many error
> > messages, some of them seem to caused by lack of "typename", others are
> > very strange, for example, about using boost::noncopyable.
> > Does someone try serialization library on GCC 3.4? Can it be compiled?
> > I suspect I am missing something. Otherwise, I would like to try to
> > the "bugs" myself.
> Hmmm, I just checked. I'm currently using gcc 3.3.1 ? Should I upgrade to
> gcc 3.4.? I seem to recall information on the list that suggested it
> be better to wait a little bit. If upgrading is a good thing - now is a
> good time for me to do it as I'm just finalizing all the changes for next
> version and just starting the "torture test torture" procedure of
> reconciliation of compiler quirks.
> Robert Ramey
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk