On 24 Aug 2010, at 13:51, Guillermo Polito wrote: > Thinking aloud. I usually don't have to write dates in my code, > because they are picked by the user. > I think that a well built kernel and nice well integrated UI widgets > (maybe I'm going out of the scope :P ) are enough in most of the > cases.
+1 I like the libraries that support to write dates and times in neat Smalltalk ways, but they should not compromise the use of date-times when handling strings coming from the UI front-end. Having a 'xxxx' asString that does not return an error when the timestring is wrong cripples that. You would essentially need to use a separate parser-checker before trying to use the basic conversion libraries for date-times. > Anyway, IMHO it's very important to review Time>>fromString: because > it's useful for serialization stuff. Like webservices and that kind > of things a lot of people have to use. > > I opened a ticket http://code.google.com/p/pharo/issues/detail?id=2854 +1 Are you already onto it? If not, I can make my hands dirty on this one ;-) _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
