[Mono-bugs] [Bug 59648][Nor] Changed - UTF8Encoding.GetChars() fails for some byte data

[bugzilla-daemon@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 sebastien@ximian.com.

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

--- shadow/59648	2004-06-07 05:55:51.000000000 -0400
+++ shadow/59648.tmp.13653	2004-06-07 09:18:53.000000000 -0400
@@ -3,21 +3,21 @@
 Version: unspecified
 OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
 Severity: Unknown
-Priority: Major
+Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: atsushi@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: UTF8Encoding.GetChars() fils for some byte data
+Summary: UTF8Encoding.GetChars() fails for some byte data
 
 UTF8Encoding.GetChars() fails to read the sequence of data shown below:
 
 using System;
 using System.IO;
 using System.Text;
@@ -67,6 +67,18 @@
 Attaching the patch.
 
 ------- Additional Comments From atsushi@ximian.com  2004-06-07 05:55 -------
 Created an attachment (id=8032)
 proposed patch
 
+
+------- Additional Comments From sebastien@ximian.com  2004-06-07 09:18 -------
+I think it's a bad idea.
+
+(a) UTF8Encoding unit tests shows that (some/most) overlong are
+catched by MS implementation.
+(b) Overlong are dangerous in many other places in the framework.
+Removing the check will open up many other holes elsewhere.
+
+Question: does this (ignore) happens only when there's remaining data
+after the overlong ? That seems to be a difference between your code
+and the unit tests.