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

On Friday 11 April 2003 04:25 pm, Bobby Thomale wrote:

I remember at one point it was mentioned that:

function

was deprecated and we were to use either the more universally supported:

functionN

or the cleaner:

function

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 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 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.

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 :( Doug