Re: [boost] Re: Build+Install+/Zc:wchar_t in Visual studio builds

From: vc (vcotirlea1_at_[hidden])
Date: 2003-11-03 10:01:50

Hi Drazen,

First of all, you replied this email to somebody, and my problem is that I
didn't
get that email from that somebody. Can you tell me please who is the person
that wrote you the email and
do you have any idea why I haven't get the email? Is because it was sent
only to you?

Second, I have a big app that uses: boost libs, my libs, other 3rd party
libs. If my choises are: add that flag either to
*all* libs (and of course .exe) or to none, then I'm not sure if I can add
that flag as maybe the other 3rd party libs
won't "like" it.
I also don't think that it is safe to add that flag _just_ to boost libs and
my libs as I can get into troubles
if some parts have this flag and some don't.
So, I really don't know what I should do ... :(

Thx,
Viv

----- Original Message -----
From: "Drazen DOTLIC" <Drazen.Dotlic_at_[hidden]>
To: "Boost mailing list" <boost_at_[hidden]>
Sent: Friday, October 31, 2003 2:54 PM
Subject: RE: [boost] Re: Build+Install+/Zc:wchar_t in Visual studio builds

> > IMHO, the build system is correct as-is --- require
> > /Zc:wchar_t, since you
> > cannot reliably build a non-trivial application that uses
> > wchar_t as a typedef
> > for unsigned short without lots of hacks. e.g.
> >
> > WORD x=someIntegerReturnedFromWin32API();
> > std::string s=boost::lexical_cast<std::string>(x);
> >
> > fails without /Zc:wchar_t on 1.30.0. This is fixed for
> > 1.30.2, but how much
> > other code has the same problems?
> >
> > I would recommend that VC7.1 users *always* have /Zc:wchar_t
> > set unless they
> > have a good reason not to, regardless whether or not they use boost.
>
> You are missing the point IMHO. Probably everyone *wants* to have it on,
> for exactly the reasons you mention above. But, not all of us have the
> luxury to do so, because we use other libraries besides boost, and
> compile our programs as a whole (using same set of flags).
>
> The questions was _not_ whether it is *required* to use this flag, but
> what should be default. Requiring means forcing, default on the other
> hand is something that can be overridden.
>
> Drazen
> _______________________________________________
> Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost
>