Re: Objective-C Question
Re: Objective-C Question
- Subject: Re: Objective-C Question
- From: Marcel Weiher <email@hidden>
- Date: Sun, 21 Sep 2003 15:40:34 +0100
While others struggle to get aop features in their language (see
http://eclipse.org/aspectj/ ) ObjC had those features ever before the
aop hype broke loose - hence the name "category" for it and not
"aspect". So this hype is an "old head" for 'Steppers and Cocoaists.
Sorry, but Categories don't address the same issues as Aspects do.
Sure they do. They don't address them in the same way and not with
precisely the same effects, but address them they do.
You can't write a Category that logs every function as it's called,
for instance.
Quite frankly, I always thought that was one of the more asinine
examples of AOP, where the concept had been dumbed down and abused. If
you want that, substitute the messenger (I assume you meant "message
send", not function call)
You can't write a Category that deals with more than one class, even,
or with anything but *one* *class*.
Sure you can.
Categories can't handle basic types, and they can't handle methods
directly.
Huh? The primitive-type issues are quite separate from AOP-issues.
Aspects, on the other hand, address Cross-Cutting Concerns,
And this is precisely what categories can be used to address. At least
*I* keep using them for cross-cutting concerns...
which by definition affect more than one thing in your program, be
they classes, objects, instances, methods, access, whatever.
Exactly.
Marcel
--
Marcel Weiher Metaobject Software Technologies
email@hidden www.metaobject.com
Metaprogramming for the Graphic Arts. HOM, IDEAs, MetaAd etc.
1d480c25f397c4786386135f8e8938e4
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.