On Tue, Nov 15, 2011 at 10:54 AM, Torsten Curdt <[email protected]> wrote: >> There’s no requirement that there be such an ivar, only a method named >> -window that returns an NSWindow*. The implementation of that method is >> arbitrary. For example it might just look like >> - (NSWindow*) window { return [_parent window];} > > But then again the compiler would know about these implementations.
You have some magical compiler that can not only access superclasses' method definitions when all it sees is a header file, but has also solved the halting problem in a way that allows it to determine how the method uses instance storage? --Kyle Sluder _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
