diff -r 000000000000 -r b1a7da25b547 test/script/basic/NASHORN-498.js
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/test/script/basic/NASHORN-498.js	Wed Apr 27 01:36:41 2016 +0800
@@ -0,0 +1,42 @@
+/*
+ * Copyright (c) 2010, 2013, Oracle and/or its affiliates. All rights reserved.
+ * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
+ * 
+ * This code is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License version 2 only, as
+ * published by the Free Software Foundation.
+ * 
+ * This code is distributed in the hope that it will be useful, but WITHOUT
+ * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+ * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
+ * version 2 for more details (a copy is included in the LICENSE file that
+ * accompanied this code).
+ * 
+ * You should have received a copy of the GNU General Public License version
+ * 2 along with this work; if not, write to the Free Software Foundation,
+ * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
+ * 
+ * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
+ * or visit www.oracle.com if you need additional information or have any
+ * questions.
+ */
+
+/**
+ * NASHORN-498 :  'in' inside conditional expression middle term confuses parser when used in for statements
+ *
+ * @test
+ * @run
+ */
+
+// no syntax error expected for the following functions
+function func() {
+    // Parser thinks it is a for-in statement! But 'in' used in 
+    // cond. expression. This is a normal for statement
+    for (var x = a ? b in c : 3;;) {}
+}
+
+function func2() {
+    // for-in statement but init is cond. expression with 'in' 
+    // This is same as "for (var x = (a? b in c : e) in {} )"
+    for (var x = a ? b in c : e in {}) {}
+}