Re: Why the need for the id type?
Re: Why the need for the id type?
- Subject: Re: Why the need for the id type?
- From: Chris Williams <email@hidden>
- Date: Tue, 19 Jun 2007 11:01:13 -0700
- Thread-topic: Why the need for the id type?
A key difference between the strict compile-time typing in the Visual
C++/.NET world vs. dynamic run-time typing of the Obj-C/Cocoa world is
performance. Every method invocation in the former is known and can be
optimized (even unrolled) at compile/link time, where dynamic calls like the
one posed by the OP involve trolling up the hierarchy at run-time in the
latter case. The performance difference can be significant.
However, in the development of GUI applications, this performance difference
is negligible compared to the IO time, and especially the user delay. I was
the manager of the Microsoft Visual Studio group at the time the .NET
framework was being developed and I can tell you that the arguments over
this topic were long and heated. In the end, the purist,
performance-oriented people won the argument, and hence the implementation
you see today. This was, IMHO, at the expense of the "ease of development"
crowd, who argued vehemently for a model more like Obj-C/Cocoa with a more
developer-friendly, loosely bound world.
FWIW, you CAN do this kind of loosely bound invocation in VC++, it's just
not widely done.
> From: Kevin Hoffman <email@hidden>
> Subject: RE: Why the need for the id type?
>
> As a .NET developer, I'd like to interject a little something here.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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