Re: [Q] inconsistent naming for Core Graphics and Foundation?
Re: [Q] inconsistent naming for Core Graphics and Foundation?
- Subject: Re: [Q] inconsistent naming for Core Graphics and Foundation?
- From: Martin Wierschin <email@hidden>
- Date: Mon, 16 Mar 2009 19:12:06 -0700
On 2009.03.15, at 1:21 AM, Ken Thomases wrote:
I think the division isn't Core Graphics vs. Foundation (or, more
generally, one framework vs. another). I think it's between legacy
and new APIs. It seems fairly clear to me that Apple has adopted a
convention that new APIs should be centered around a type, and that
names within such an API are to start with the name of the type.
I for one really love this naming scheme and wish it was consistent
across all frameworks. So many times I've forgotten an identifier
that was immune to discovery via autocomplete, eg:
NSMacOSRomanStringEncoding. Sure you can look it up in the
documentation/headers, but it's a diversion. It's too bad we have all
the legacy stuff.
~Martin
_______________________________________________
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