Re: [boost] py_cpp does not like STLport (STLport bug revealed)

From: David Abrahams (abrahams_at_[hidden])
Date: 2000-11-06 16:10:45

On second look at the conditional, it looks like a brain-o. Clearly if
__STL_MSVC is not defined, it is <= 1200. I think the author meant this:

# if !(defined(__STL_MSVC) || (__STL_MSVC <= 1200))

----- Original Message -----
From: "Petr Kocmid" <pkocmid_at_[hidden]>
To: "boost mailing list" <boost_at_[hidden]>
Sent: Monday, November 06, 2000 3:56 PM
Subject: [boost] py_cpp does not like STLport (STLport bug revealed)

> Hi.
>
> On MSVC 6.4 with STLport 4.0, py_cpp fails to compile
> reporting
> error C2039: 'type_info' : is not a member of '_STL'
> at every usage of std::type_info.
>
> Without STLport, everything builds ok.
>
> looking inside the STLport's <typeinfo> header, it
> seems the stuff is placed into global instead of std:
> ----------thisisthefragmentofcopyrightedstlportcode
> # if defined  (__STL_USE_NAMESPACES) \
>    && ( defined (__STL_VENDOR_GLOBAL_EXCEPT_STD) || defined
> (__STL_USE_OWN_NAMESPACE) || defined (__STL_DEBUG))
> __STL_BEGIN_NAMESPACE
>
> // VC++ 6 has only this guy in ::
> # if !(defined(__STL_MSVC)&& (__STL_MSVC <= 1200))
> using __STL_VENDOR_EXCEPT_STD::type_info;
> # endif
> ---------------------------------------------------
>
> After I realised, that py_cpp code is ok on native
> headers with std::type_info, I removed that conditional
> under the comment from STLport and it worked as a good
> fix for me.
>
> Maybe stlport tries to workaround some issue
> already solved by Service Pack 4.
>
> Is it possible for anyone with latest STLport beta to
> have a look on this? Otherwise we shall report a bug
> to STLport.
>
> Petr Kocmid
> pkocmid_at_[hidden]
>
>
>
>