On Fri, May 15, 2009 at 11:00 PM, Tron Thomas wrote:
> Greg Parker wrote:
>>
>> On May 14, 2009, at 9:58 PM, Tron Thomas wrote:
>>>
>>> That did the trick. The stack trace allowed me to track down the cause
>>> of the error. Because Objective-C++ does not have a concept of class static
>>> varia
Greg Parker wrote:
On May 14, 2009, at 9:58 PM, Tron Thomas wrote:
That did the trick. The stack trace allowed me to track down the
cause of the error. Because Objective-C++ does not have a concept of
class static variables I had an NSArray defined in an anonymous
namespace in the implementa
Greg Parker wrote:
On May 14, 2009, at 9:58 PM, Tron Thomas wrote:
That did the trick. The stack trace allowed me to track down the
cause of the error. Because Objective-C++ does not have a concept of
class static variables I had an NSArray defined in an anonymous
namespace in the implementa
On May 14, 2009, at 9:58 PM, Tron Thomas wrote:
That did the trick. The stack trace allowed me to track down the
cause of the error. Because Objective-C++ does not have a concept
of class static variables I had an NSArray defined in an anonymous
namespace in the implementation module that
Clark Cox wrote:
On Thu, May 14, 2009 at 6:43 PM, Tron Thomas wrote:
I am writing a Cocoa application that links to many frameworks. For some
reason when I debug the program the following message appears in the debug
output:
*** _NSAutoreleaseNoPool(): Object 0x409660 of class NSCFArray au
On Thu, May 14, 2009 at 6:43 PM, Tron Thomas wrote:
> I am writing a Cocoa application that links to many frameworks. For some
> reason when I debug the program the following message appears in the debug
> output:
>
> *** _NSAutoreleaseNoPool(): Object 0x409660 of class NSCFArray autoreleased
> w
