Re: [boost] Re: Problem with config_05.zip

From: Howard Hinnant (hinnant_at_[hidden])
Date: 2001-07-26 15:17:29

Thanks for the cage rattling Chris.  I was asleep at the keyboard. :-)

Chris's description is correct.  Metrowerks C headers will define 
__MSL__.  Metrowerks C++ headers will define __MSL_CPP__ (and may or may 
not also define __MSL__ depending on whether they include a C header).  
The compiler will define  __MWERKS__ (with no need to include 
anything).  They are all best interpreted as hexadecimal numbers, will 
always increase in future versions, and are typically different from 
each other.  This is all true in Pro 5 as well.

-Howard

On Thursday, July 26, 2001, at 03:52  PM, Chris Little wrote:

> Daryle,
>
> I don't work for Metrowerks but I will give it a try.
>
> I'm using CWP 6.2.  __MSL__ is only defined by including headers from 
> MSL's C library.  The MSL C++ defines __MSL_CPP__ in mslconfig which is 
> included by utility.  I don't have CWP 5 to check and see if this is 
> defined for CWP 5 as well.
>
> I've cc'd Howard Hinnant, who does work for Metrowerks and is the 
> current author of MSL's C++ library.  He may be able to give you a 
> better answer.
>
> Chris
>
> > -----Original Message-----
> > From: Daryle Walker [mailto:darylew_at_[hidden]]
> > Sent: Thursday, July 26, 2001 2:28 PM
> > To: boost_at_[hidden]
> > Subject: [boost] Re: Problem with config_05.zip
> >
> >
> > on 7/26/01 6:51 AM, John Maddock at John_Maddock_at_[hidden] wrote:
> >
> > [SNIP]
> > > So the question is:  is including <utility> sufficient to
> > result in __MSL__
> > > getting defined?  It looks not.  BTW I choose <utility>
> > here because it's
> > > by far the most lightweight of the standard lib headers. 
> > The other errors
> > > that you're seeing are all resulting from that
> > mis-detection.  Any ideas
> > > what I need to include to locate __MSL__ if it's defined?
> >
> > Is there anyone on this list that is a Metrowerks engineer
> > that can answer
> > this question?  (Remember, I'm using CodeWarrior Pro 5, so a CWP6-only
> > solution won't work for me.)  It should be a header that other
> > implementations would have too, so John won't have to add a
> > lot of #ifdefs
> > and #includes.
> >
> > --
> > Daryle Walker
> > Mac, Internet, and Video Game Junkie
> > darylew AT mac DOT com
>
>
> Info: http://www.boost.org  Unsubscribe: <mailto:boost-
> unsubscribe_at_[hidden]>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.