[Mono-bugs] [Bug 78569][Maj] Changed - DateTime.Parse fails to use culture info

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by atsushi at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=78569

--- shadow/78569	2006-06-07 03:06:56.000000000 -0400
+++ shadow/78569.tmp.25390	2006-06-07 04:33:18.000000000 -0400
@@ -114,6 +114,14 @@
 ------- Additional Comments From peter at novonyx.com  2006-06-07 03:06 -------
 I'm about to go to bed and don't have sourcecode here, but if I 
 remember correctly, there was code on the unmanaged side that 
 mirrorred the order on the managed side. Maybe I missed putting a 
 variable in the right order? I'll have a look tomorrow. Odd that it'd 
 be only in a particular locale, though. It should break on all.
+
+------- Additional Comments From atsushi at ximian.com  2006-06-07 04:33 -------
+Other cultures might have got broken as well. For this particular
+case, there is another matching pattern M/d/yyyy h:mm:ss in en-GB
+DateTimeFormat (try new CultureInfo
+("en-GB").DateTimeFormat.GetAllDateTimePatterns()). For such cultures
+that do not have conflicting date time patterns wouldn't have been
+affected.