Re: Cocoa et al as HCI usability problem
Re: Cocoa et al as HCI usability problem
- Subject: Re: Cocoa et al as HCI usability problem
- From: Andy Lee <email@hidden>
- Date: Mon, 19 May 2008 19:18:30 -0400
On May 19, 2008, at 6:06 PM, Peter Duniho wrote:
Date: Mon, 19 May 2008 15:51:07 -0400
From: Andy Lee <email@hidden>
* Objective-C allows you to create categories, effectively modifying
a class's interface at runtime.
C# provides "partial" class implementations for when you want to
split functionality across multiple module files (one use of
categories). When doing this, you have complete access to the
class's private and protected members, and the implementation is
truly part of the class.
When you are accessing only the public API for a class, C#'s
extension methods provide the same sort of syntax, but via static
methods that the compiler handles so as to make them look like they
are part of the original class.
Interesting. When you say static methods, do you mean methods that
cannot access instance internals? What does self (or this, or
whatever) refer to in those methods?
Someone else addressed the IB implementation question, in a far more
authoritative way than I could have, so I'll leave that one alone.
Yeah, maybe I should have left it alone too. :) IB is better fodder
for advocating languages with reflection/introspection than dynamic
messaging.
--Andy
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden