On Tue, 21 Mar 2006, Garrett, Philip (MAN-Corporate) wrote:
My aversion is more philosophical than practical. I'm working on internationalizing some software right now, and (of course) one of the main goals is to decouple presentation from data. I chose DateTime for my date needs only to later find that the presentation (locale/output time zone) for this core support module is embedded in its data. It's the very thing I've been struggling against for months. I'm actually quite surprised that *you* don't see this as a problem.
The alternative would be to require a locale object to be passed in to every call to month_name(), month_abbr(), day_name(), and day_abbr(). Philosophical purity of design lost out over massive convenience in use.
Now, I could allow an _optional_ locale object argument if that'd make it easier for folks to use. But I certainly don't want those methods to blow up if you call them without any args.
-dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/
