Re: ObjC++ (and a word about Java, too ;-)
Re: ObjC++ (and a word about Java, too ;-)
- Subject: Re: ObjC++ (and a word about Java, too ;-)
- From: Eric Schlegel <email@hidden>
- Date: Wed, 5 Dec 2001 08:46:17 -0800
On Wednesday, December 5, 2001, at 08:32 AM, Thomas Lachand-Robert
wrote:
It is very difficult to understand what happens. Compare with a similar
piece in Cocoa:
NSDictionary *fattrs = [file attributes];
NSDate* date = [fattrs objectForKey:NSFileModificationDate];
NSString *group = [fattrs objectForKey:NSFileGroupOwnerAccountName];
NSString *owner = [fattrs objectForKey:NSFileOwnerAccountName];
Exception removes the need of "status", classes and dictionaries don't
need strange names, etc.
I can't deny that if you have the luxury of a custom language runtime,
you can do some nice things to simplify the code. Carbon is definitely
meant to be a procedural API that's available from multiple languages,
including non-OO languages.
And for the three frameworks: Cocoa, Carbon, Java? Assuming than OS 9
disappear, I can't see the need to keep Carbon.
Well, there a few large developers named Microsoft, Adobe, Corel, Quark,
FileMaker who are responsible for many of our hardware sales who might
disagree with you there. But at any rate; this isn't the place for a
debate on Carbon vs. Cocoa. Thanks for your thoughts!
-eric