Re: [Q] COM and dynamic link library?
Re: [Q] COM and dynamic link library?
- Subject: Re: [Q] COM and dynamic link library?
- From: Scott Thompson <email@hidden>
- Date: Tue, 18 Apr 2006 22:25:53 -0500
On Apr 18, 2006, at 4:37 PM, Ondra Cada wrote:
Nowhere there is any place for the essentially non-object-oriented
COM model. I guess it perhaps might be used for Carbon plug-ins
(whose C++ limitations do not allow for a decent plug-in
architecture based on the language runtime), but definitely *not*
for Cocoa ones.
Now now... "C++ limitations" indeed. You know better than that :-)
First of all, there is no C++ in Carbon. Carbon is strictly a C
API. From every conversation I've had on the subject, Apple has done
this intentionally to avoid annoying dependencies on specific C++
compilers.
But more to your point, there is nothing preventing a Carbon
application from using Objective-C too (as I'm sure you well know).
The Objective-C plugin model you describe could be used just as
easily (and effectively) in a Carbon application as it is in a Cocoa
application. In fact, many of the newer and more interesting
technologies in Mac OS X (WebKit, Core Image, Core Data, etc..) can
be used from Carbon applications that are willing to add a little
Objective-C code.
In fact, mixing Carbon and Objective-C is a learning experience worth
exploring. It's good for the soul.
In fact, I suspect the OP is referring to CFPlugin which is part of
the Core Foundation layer and, therefore, lies beneath Carbon, Cocoa,
and can even be used from the BSD application layer. Given that, I
suspect that CFPlugin can be used in levels of the operating system
where the Objective-C runtime is not available. I don't have any
specific instances that might back up that assertion... but it
certainly seems possible.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden