Implementation wise (and this is not to be relied on), when you begin
observing an object, the object's class is dynamically subclassed, and
the property accessors are overridden. The overrides call the
original implementation and also do the notification of interested
parties. The original object changes class so that it is now an
instance of the subclass.
When you stop observing, the object's class changes back to the
original class.
An inlining JIT would have trouble with this.
Why would that be the case? AOP is usually done through byte code
transformation and that's one layer above.
Anyway ...I think this is getting OT
cheers
--
Torsten
_______________________________________________
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 [EMAIL PROTECTED]
