Re: v1.7 Changed Something with Types?

[James W. W. <ja...@fr...>]

Seth Willits <bm...@pa...> wrote

>>  It compiles with no warnings or errors.  Are you defining
>>QUESA_OS_MACINTOSH or QUESA_OS_COCOA?  When using CodeWarrior,
>>Quesa.h will automatically turn on QUESA_OS_MACINTOSH, but it looks
>>like XCode users must do it themselves.
>
>Yup. It's in my prefix header. It must have something to do with a
>change between the two versions. Could the change to C++ have
>changed this?

I don't see how.  That's an internal change that should not affect 
the public headers, and the public headers are all that you're using.

Without being able to reproduce the problem, I can't help.  Can you 
make a sample project that has this problem, and post it somewhere?
-- 
   James W. Walker, ScriptPerfection Enterprises, Inc.
   <http://www.write-brain.com/>