Oh. I can't even really use this. I don't know what I need to associate at runtime, at which point I know what it is by a string value. Since I can't use a string value as a key, I can't really make the association. I could associate an NSMutableDictionary, but if I do that, I may as well just make that a member of my base class.
On Oct 8, 2010, at 17:12:28, Kyle Sluder wrote: > On Fri, Oct 8, 2010 at 5:00 PM, Rick Mann <rm...@latencyzero.com> wrote: >> Yes, I read that. I had hoped that I'd be able to add ivars before the class >> was instantiated. In this case, the class is being loaded dynamically at run >> time. Is there no way to get in the middle of the load and add an ivar? >> >> In any case, sure seems like I ought to be able to do it in +initialize. > > The documentation states you can't add ivars to classes that have > already been registered. In order for a class to receive +initialize, > it logically must already have been registered with the runtime. > Therefore, it's quite apparent why class_addIvar() can't be called > from +initialize. > > The fact that you want to add instance variables to a class at all is > a terrible code smell. Like Fresh Kills Landfill bad. What are you > trying to achieve? > > --Kyle Sluder _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
