Re: [Boost-users] [Serialization] Status of bug in 1.33?

From: Robert Ramey (ramey_at_[hidden])
Date: 2006-03-08 21:57:16

Adjustments have been made to the current CVS head to address this
problem.  So the symptom should disappear with 1.34.  Feel free
to downlaod the lastest CVS and double check.

Robert Ramey

Andrew Lin wrote:
> Hi everyone,
>
> Some time back I wrote asking about a problem I was having with the
> 1.33
> serialization library which turned out to be a bug:
>
> http://lists.boost.org/boost-users/2005/12/15969.php
>
> In short, custom archives had some kind of compilation failure which I
> never really understood, but which didn't fail in 1.32.
>
> Does anyone know what ever came of this?  Is there a bug tracker
> where I
> can follow its status?  (I didn't see it in the 1.33.1 release notes,
> so
> I'm assuming it's still broken.)  I thought I'd be able to use 1.32
> until 1.34 came out, but something has come up in the project which
> would be perfect for the multi_index library with hashing, new in
> 1.33.
>
> Thanks,
> Andrew
>
> =============================================================================================
> Email transmissions can not be guaranteed to be secure or error-free,
> as information
> could be intercepted, corrupted, lost, destroyed, arrive late or
> incomplete, or contain viruses.  The sender therefore does not accept
> liability for any errors or omissions in
> the contents of this message which arise as a result of email
> transmission.  In addition,
> the information contained in this email message is intended only for
> use of the
> individual or entity named above.  If the reader of this message is
> not the intended recipient, or the employee or agent responsible to
> deliver it to the intended recipient,
> you are hereby notified that any dissemination, distribution, or
> copying of this communication, disclosure of the parties to it, or
> any action taken or omitted to be taken in reliance on it, is
> strictly prohibited, and may be unlawful.  If you are not the
> intended recipient please delete this email message.
> ==============================================================================================