[Mono-bugs] [Bug 52286][Blo] New - mjs, can't parse new expression without parameters.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 8 Mar 2004 18:23:42 -0500 (EST)


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 gerardo@ximian.com.

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

--- shadow/52286	2004-03-08 18:23:42.000000000 -0500
+++ shadow/52286.tmp.19235	2004-03-08 18:23:42.000000000 -0500
@@ -0,0 +1,60 @@
+Bug#: 52286
+Product: Mono: Compilers
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Blocker
+Component: JScript
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: cesar@ciencias.unam.mx               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: mjs, can't parse new expression without parameters.
+
+Description of Problem:
+There's one missing rule from Ecma-262 spec about new expressions.
+See section 11.2 from Ecma-262 spec, it says:
+
+NewExpression:
+  MemberExpression
+  new NewExpression
+
+The second rule is missing on our grammar due to non-determinism problems.
+The problem comes from subrule "new MemberExpression Arguments" from rule
+MemberExpression (see section 11.2 from Ecma-262).
+
+1. cd mcs/class/Microsoft.JScript
+2. make
+3. cp ../lib/Microsoft.JScript.dll /usr/local/lib
+4. cd Microsoft.JScript
+5. mcs -r Microsoft.JScript.dll -o mjs.exe driver.cs
+6. Write to a file, let's say new.js:
+
+        new object;
+
+7. Execute: mono mjs.exe new.js
+
+Actual Result:
+Unhandled Exception: line 1:8: expecting "OPEN_PARENS", found ';'
+
+
+Expected Results:
+Parsing phase ended succesfully.
+
+How often does this happen? 
+Always.
+
+Additional Information:
+Look rules: new_expr and member_expr at jscript-lexer-parser.g
+
+Version:
+
+mono, mcs 's cvs versions from december 17, 2003.
+
+------- Additional Comments From gerardo@ximian.com  2004-03-08 18:23 -------
+*** Bug 55285 has been marked as a duplicate of this bug. ***