Re: [Boost-Users] More Mac Compiler Woes - Boost 1.30.0 - Thread and type_traits

From: Bobby Thomale (bobby-thomale_at_[hidden])
Date: 2003-05-05 13:08:37

>> I remember at one point it was mentioned that:
>> 
>> function<type, type...>
>> 
>> was deprecated and we were to use either the more universally supported:
>> 
>> functionN<type,type...>
>> 
>> or the cleaner:
>> 
>> function<void myfuncSig()>
>> 
>> instead if our compiler supported it.
>> 
>> (Mine doesn't support that last one yet I don't think.)
>> 
>> I am guessing that the oldest syntax was removed and no one has bothered to
>> update the Mac carbon thread implementaton to compile again since then?
>> 
>> That one seems pretty easy to fix - just update to a supported syntax?  (I
>> could do this, update to the functionN<type,type...> syntax since that is
>> what my compiler supports.  If someone wants me to make and submit the
>> changes to them for inclusion I'd be happy to, if I knew who to send them
>> to...)
>> 
>> Or is there a better/easier workaround?
> 
> Sorry, I completely missed this message this first time around. For
> CodeWarrior you'll need to use the functionN<type, type...> syntax with
> Boost.Function. 
> 
> William Kempf is the author/maintainer of Boost.Threads and Mac Murrett
> contributed the Mac carbon implementation. If you would put together a patch
> using the appropriate functionN classes it would be appreciated, and I'm sure
> Bill Kempf would accept it.

Ok.  I have already made the changes locally.  Do you want me to just send
them to Bill then? 

>> Secondly, the Signals library is not compiling.  It's actually not a
>> Signals problem, I think it is a type_traits problem.
> 
> Odd. It sounds like a compiler problem, but our Win32 regression tests show
> Signals working properly with CodeWarrior 8.3. We don't have any regular
> regression testing for CodeWarrior on the Mac, unfortunately :(

Huh.  It is definitely broken - someone else posted about it earlier today,
too.  

Well, I wasn't sure what to do about it.  My thought was that CodeWarrior
should be using the same "broken compiler workaround" that the other
compilers were using.

I will send you the change I made.  It makes it compile all right but I have
no idea if it is the right thing or not...  (I don't exactly understand the
type-traits source.  :-)

Are you the right person to take a look at it and (possibly) add it to the
Boost sources?  

                                -- Bobby

---------------------------------------------------------------------
Bobby Thomale
Senior Software Developer
Inoveon Corporation
http://www.inoveon.com/
---------------------------------------------------------------------