Re: [NSDate +dateWithNaturalLanguageString] question
Re: [NSDate +dateWithNaturalLanguageString] question
- Subject: Re: [NSDate +dateWithNaturalLanguageString] question
- From: Charles Srstka <email@hidden>
- Date: Mon, 14 Jul 2008 00:34:50 -0500
On Jul 13, 2008, at 7:47 PM, Deborah Goldsmith wrote:
The Thai, Hebrew, and Islamic calendars are quite important in the
software market, and there is one other that Jens didn't mention:
the Japanese calendar. The Japanese era system is heavily used in
Japan: http://en.wikipedia.org/wiki/Japanese_era_name
While the months and days of the Japanese calendar match the
Gregorian calendar, the years and eras do not, and you need
NSCalendar to handle that.
Mac OS X 10.5 supports Gregorian, Japanese, Thai, Hebrew, and
Islamic (two kinds) calendars.
What I don't get is why there can't just be a
+dateWithYear:month:day:hour:minute:second:timeZone:calendar: method
to replace the current
+dateWithYear:month:day:hour:minute:second:timeZone: one instead of
having to deal with three different classes just to do a simple task
that used to require only one class method. You'd just put the
calendar you wanted to use in the last parameter (or pass nil to just
use the current calendar) and it would do the right thing. Granted,
this seems like the sort of thing that would be pretty easy to do with
a category on NSDate, but I'm just curious why it wasn't included with
the standard distribution.
Charles
_______________________________________________
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