Re: .Mac support to C/C++ application
Re: .Mac support to C/C++ application
- Subject: Re: .Mac support to C/C++ application
- From: Rich Wardwell <email@hidden>
- Date: Mon, 24 Apr 2006 01:19:15 -0500
Actually, I think I do have a pretty good understanding... I'm no
Cocoa expert... more of a Cocoa newb... but I've been coding in C, C+
+, and Java for 20+ years. You proved the point in your 2nd
paragraph -- Apple at one point did support an Apple wrapper to some
(all?) of Cocoa. It may be an ObjC API at this point -- but it's an
API to a bunch of functionality that could be made available to
multiple languages.
Cocoa is a library / framework. It provides a nice abstraction of a
bunch of nice stuff. An OO language would be worthless without a
framework to provide me access to operating system constructs. I
mean, sure, you could probably write your own GUI layer and
components that looked and acted something like Aqua. It would also
take a couple years. Do you want to reverse-engineer the .mac
protocols?
Just as Java is really two things today -- 1) an object-oriented C-
syntax programming language... and 2) a huge library of
functionality, from GUI toolkit to I/O to web abstractions. In the
case of Java, they are intrinsically tied together. C# and .NET --
same deal, except MS has allowed the implementation language and the
library to be pretty much interchangeable. I can do C++, VB, C#
against libraries and such written in C++, VB, and C#. Obviously, a
managed / VM based environment is part of this - although I think
what I'm referring to could be done with a few language / linker
changes and some fancy wrappers... (ok, maybe that's a bit of an
oversimplification! :)
Rich Wardwell
Software Developer (Java, C++), Mac Fanatic
On Apr 24, 2006, at 12:55 AM, Paul Lynch wrote:
On 24 Apr 2006, at 06:28, Rich Wardwell wrote:
With the plethora of "Switchers" coming from C/C++/(even Java)
land (including myself), I'm starting to get a little sick and
tired of having the faint feeling that Objective-C is being
rammed down my throat at every turn just to have access to fairly
critical / important APIs that are only found in Cocoa.
As a non-switcher, I am also sick and tired. Of important APIs
that *aren't* available as part of Cocoa.
I think you may be under a slight misunderstanding: Cocoa is an
ObjC API. You can't call it without using ObjC, because it uses
language constructs that depend on the OO nature of ObjC. The java
version of Cocoa (which now seems to be deprecated) notwithstanding.
If you want to use a decent API, then learn an OO language,
please. Otherwise you'll get stuck with with the primitive APIs
that are available for incomplete OO languages.
Paul
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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