From: David Abrahams (dave_at_[hidden])
Date: 2004-07-05 15:53:04
François Dumont <francois.cppdevs_at_[hidden]> writes:
> I am currently actively contributing to STLport. One of my
> contribution is to make boost and STLport closer. I think STLport can
> gain a lot in using some of the boost libraries and then boost will be
> able to count on a robust std lib.
> For the moment I only use 2 libraries from boost, type_traits and
> call_traits. I have some issue when I include the boost headers from
> STLport. I was counting on the BOOST_STD_CONFIG macro to limit the
AFAIK we don't have such a macro, at least not a documented one.
> but for some platforms this feature is just useless. Under Win32
> there is a workaround implemented for MSVC compilers (win32.hpp:60)
> on the min and max template functions. This workaround require the
> inclusion of the algorithm standard header which make the STLport
> lib build process failed.
I'm not exactly sure what you're referring to, but there's been some
recent work on dealing with the horrible min/max macros that some
headers define. Please search our mailing list archives for recent
postings from Eric Niebler.
> According the comment this workaround has not really been
The comment where?
> validated so my questions are:
> - is it require for all MSVC++ versions? Doesn't VC.Net 2003 or
> even 2002 managed the described cases correctly?
> - Couldn't this workaround be implemented for the native library
> only and not when using STLport? STLport looks to me as the right
> place to handle this case.
I don't think you're giving enough specifics for most of us to
understand what you're talking about. Please point to specific source
code in the Boost CVS.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk