-
@mjtsai As NSWindowAuxilary isn't public, Apple can add and remove ivars as needed without having the fragile base class problem.
Marcel Weiher
Rosyna Keller
Michael Tsai
@rosyna So why are they still using it now that we have Objective-C 2?
-
-
@mjtsai As long as the 32-bit i386 runtime exists, they can't dump the ivars from the headers, sadly. -
@rosyna So, again, this is not (yet) an actual performance improvement resulting from Objective-C 2. -
@mjtsai While NSWindow may have been good to show the pain of fragile base classes, it may have been bad for an optimization example -
@mjtsai a better example would be NSStringDrawing, all the Gesture Recognizer classes, NSIndexPath, various NSCollectionView classes - View other replies
-
@rosyna Interesting that they added hash ivar for NSIndexPath. NSStringDrawing is a category so not sure what you are referring to there. -
@mjtsai err, NSStringDrawingContext.
-
-
@mjtsai Non-fragile ivars require the modern runtime, which on Mac OS X, is only available in 64-bit processes.
Jim Correia
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.