[Mono-dev] DateTime.Parse difference with .NET

Alfredo Jose Muela Romero aioros at ono.com
Tue Aug 9 04:27:31 EDT 2005


El Tue, 09 Aug 2005 13:30:19 +0900
Atsushi Eno <atsushi at ximian.com> escribió:

> Hello,

> In fact using DateTime.Parse() is somewhat stupid ;-) Read
> here:
> http://msdn.microsoft.com/msdnmag/issues/05/03/CultureInfo/default
> .aspx?side=true#a
> 	The DateTime.Parse method in the Microsoft .NET Framework
> 	has goals much like its predecessors, but unfortunately
> 	it suffers from some of the same problems. The code is
> 	slower since the extra checking takes time, and there
> 	will always be some new format that is not properly
> 	detected. In those older products, you may remember, the
> 	behavior was sometimes disparagingly referred to as "evil
> 	date parsing."
> At least DateTime.Parse() is COM dependent where the behavior
> is totally unpredictable and not countable from
> DateTimeFormatInfo.

	But in [1] we find that format string we need to specify as a
valid format (see Globalization.DateTimeFormatInfo) it is
unfinished :-S

	May be I lost something... what do you suggest to use instead of
DateTime.Parse() or DateTime.ParseExact()?


More information about the Mono-devel-list mailing list