Sorry to top-post, but I just wanted to note that this *wasn't* fixed in
the recent 0.5 release, and adding
#include <ciso646>
To parse_specific.hpp still solves the problem.
Thanks
Erik
-----Original Message-----
From: Nelson, Erik - 2 [mailto:eri...@ba...]
Sent: Wednesday, January 20, 2010 6:25 PM
To: C++ Networking Library Developers Mailing List
Subject: Re: [cpp-netlib-devel] Compiling server sample with VS2008 &
boost 1.41
Dean Michael Berris wrote:
> I think it's because vendors aren't quick to support them natively in
> the compiler. GCC takes this in stride just fine as does other vendors
> (Intel's compiler is another one I know that works pretty well). I
> would quote the appropriate parts of the C++ standard if I had a copy
> (which I promise I should buy someday soon) but anyway it's something
> really annoying to me for non-conformant compilers
> like MSVC.
>
> I also like them better but unfortunately to support more compilers
> we're going to have to stick with !, ||, && et al.
I'd say just put #include <ciso646> up high and continue to use them.
They are standard C++, and they're much more descriptive than the !&&#||
stuff. Don't cave in to the noncompliant compiler vendors!
Erik
|
