[Mono-bugs] [Bug 34752][Nor] New - mcs does not recognize 0xA0 (nonbreaking space) as whitespace

[bugzilla-daemon@rocky.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 mathpup@mylinuxisp.com.

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

--- shadow/34752	Fri Nov 29 04:18:55 2002
+++ shadow/34752.tmp.17364	Fri Nov 29 04:18:55 2002
@@ -0,0 +1,57 @@
+Bug#: 34752
+Product: Mono/MCS
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: mathpup@mylinuxisp.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: mcs does not recognize 0xA0 (nonbreaking space) as whitespace
+
+Description of Problem: 
+ 
+mcs complains of parsing errors when encountering nonbreaking space (ASCII 0xA0). 
+According to the ECMA 9.3.3, any character with Unicode class Zs, which includes 0xA0, 
+is whitespace. 
+ 
+http://www.unicode.org/Public/3.2-Update/PropList-3.2.0.txt 
+ 
+Steps to reproduce the problem: 
+1. Attempt to compile the attached program. 
+ 
+ 
+Actual Results: 
+syntax error, expecting BOOL BYTE CHAR DECIMAL DOUBLE EVENT FLOAT INT LONG 
+NEW OBJECT SBYTE SHORT STRING UINT ULONG USHORT VOID CLOSE_BRACE 
+OPEN_BRACKET IDENTIFIER 
+cast2.cs (7,1), Token: ERROR detail:    : Parsing error 
+Mono.CSharp.yyParser.yyException: irrecoverable syntax error 
+in <0x006fa> 00 Mono.CSharp.CSharpParser:yyparse (Mono.CSharp.yyParser.yyInput) 
+in <0x0006f> 00 Mono.CSharp.CSharpParser:parse () 
+ 
+error CS5001: Program cast2.exe does not have an entry point defined 
+Compilation failed: 1 error(s), 0 warnings 
+ 
+ 
+ 
+Expected Results: 
+ 
+Successful compilation 
+ 
+How often does this happen?  
+ 
+Always 
+ 
+Additional Information: 
+ 
+I'm surprised that this hasn't come up before. Someone sent me some C# code that he 
+had edited with VS.NET. I was surprised at the errors, so I took a look with a hex editor 
+and discovered the 0xA0 chars.