[Mono-bugs] [Bug 52352][Wis] New - IDENTIFIER lexical rule, incomplete.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sun, 19 Sep 2004 21:03:04 -0400 (EDT)


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 cesar@ciencias.unam.mx.

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

--- shadow/52352	2004-09-19 21:03:04.000000000 -0400
+++ shadow/52352.tmp.17919	2004-09-19 21:03:04.000000000 -0400
@@ -0,0 +1,55 @@
+Bug#: 52352
+Product: Mono: Compilers
+Version: unspecified
+OS: unknown
+OS Details: 
+Status: RESOLVED   
+Resolution: FIXED
+Severity: Unknown
+Priority: Wishlist
+Component: JScript
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: cesar@ciencias.unam.mx               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: IDENTIFIER lexical rule, incomplete.
+
+At mcs/class/Microsoft.JScript/Microsoft.JScript/jscript-lexer-parser.g,
+there's a rule named IDENTIFIER, currently it's defined with a simple set
+of rules, but it's not the one that's on EcmaScript-262 spec.
+
+Take a look to it and fix it (section 7.6 from Ecma-262 spec, page 14).
+
+Basically, find out the ranges for  Lu, Ll, Lt, Lm, Lo, Nl, Mn, Mc, Nd, Pc,
+on the Unicode spec.
+
+To test it, you will need to compile the parser and lexer, in order to
+achive that, you need the antlr.runtime.dll. I've put one, at:
+
+http://ada.fciencias.unam.mx/~olopez/antlr.runtime.dll
+
+In order to recreate the parser and lexer, execute:
+
+1) java -cp /classpath/to/antlr antlr.Tool jscript-lexer-parser.g
+
+I'm assuming you already have antlr-2.7.2 on your system, if you don't have
+it, just download it from: http://antlr.org/. Unpack it. And you classpath
+for it, it's PREFIX/antlr-2.7.2
+
+2) Go to mcs/class/Microsoft.JScript, execute 'make'. You'll get the new
+Microsoft.JScript.dll at mcs/class/lib
+
+3) Copy mcs/class/lib/Microsoft.JScript.dll to
+mcs/class/Microsoft.JScript/Microsoft.JScript or /usr/local/lib
+
+4) Go to mcs/class/Microsoft.JScript/Microsoft.JScript
+
+5) mcs -r Microsoft.JScript.dll -o mjs.exe driver.cs
+
+You have now the compiler, just execute: mono mjs.exe your_tests.js to test
+your rules.
+
+------- Additional Comments From cesar@ciencias.unam.mx  2004-09-19 21:03 -------
+This got fixed with Rhino's parser port to C#, that's being used now.