Re: Debugging "attempt to insert nil value" on customer's machine
Re: Debugging "attempt to insert nil value" on customer's machine
- Subject: Re: Debugging "attempt to insert nil value" on customer's machine
- From: Gideon King <email@hidden>
- Date: Thu, 16 Sep 2004 05:03:13 +1000
Thanks for the suggestions, but I haven't managed to get the
replaceSelector idea working, and have spent quite some time trying to
get the subclassing NSMutableDictionary and posing to work (which meant
using a different solution than what you proposed due to the fact that
you can't add instance variables when using PoseAsClass:). I had to
implement every initialization message, but even then, some objects are
getting instantiated in some other way than the init methods (!?). It
looks like this is a no go too.
Does anyone have any other ideas?
Thanks
Gideon
On 14/09/2004, at 11:28 PM, Ondra Cada wrote:
Me neither, but I *suspect* (really do *not* know) those
CoreFoundation "toll-free bridged" uglies are not quite ObjC classes
and just don't support poseAsClassing (and more) properly. At least,
they did bring havoc to the mutability concept and class distinctions,
and it is quite plausible suspection they broke much more :(((
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden