Re: [boost] [serialization] Linker errors in trunk

Subject: Re: [boost] [serialization] Linker errors in trunk
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-08-31 08:16:53

Robert Ramey wrote:
> Hartmut Kaiser wrote:
> >>>
> >>> Since the latest changes in trunk I'm seeing linker errors while
> >>> linking with the serialization library (VS2005 SP1,
> >>> boost_serialization-vc80-mt-gd-1_40.lib):
[snip]
> >>> boost::archive::archive_exception::archive_exception(
> >>>    enum boost::archive::archive_exception::exception_code,
> >>>    char const *,char const *);
> >>>
> >>> (note the missing underscore in exception_code)
> >>>
> >>> If I change the first parameter of the archive_exception
> >>> constructor to be a 'int' everything builds fine.
> >>
> >> Ok, I solved it. The MS header file excpt.h has a
> >>
> >>   #define exception_code _exception_code
> >>
> >> which leads to problems if not consistently included. Doh! What a
> >> mess.
> >>
> Hmmm - let's think about this a little bit.  We could
> change "exception_code" to something else.  I don't
> think it would break user code since user code
> might refer to the enum member names rather than
> the "exception_code".

Could you use BOOST_PREVENT_MACRO_SUBSTITUTION as is done for min/max?

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.