1.1 --- a/test/script/basic/javaarrayconversion.js Tue Aug 19 20:43:03 2014 +0100 1.2 +++ b/test/script/basic/javaarrayconversion.js Wed Aug 20 10:25:28 2014 +0200 1.3 @@ -1,21 +1,21 @@ 1.4 /* 1.5 * Copyright (c) 2010, 2013, Oracle and/or its affiliates. All rights reserved. 1.6 * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. 1.7 - * 1.8 + * 1.9 * This code is free software; you can redistribute it and/or modify it 1.10 * under the terms of the GNU General Public License version 2 only, as 1.11 * published by the Free Software Foundation. 1.12 - * 1.13 + * 1.14 * This code is distributed in the hope that it will be useful, but WITHOUT 1.15 * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 1.16 * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License 1.17 * version 2 for more details (a copy is included in the LICENSE file that 1.18 * accompanied this code). 1.19 - * 1.20 + * 1.21 * You should have received a copy of the GNU General Public License version 1.22 * 2 along with this work; if not, write to the Free Software Foundation, 1.23 * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 1.24 - * 1.25 + * 1.26 * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA 1.27 * or visit www.oracle.com if you need additional information or have any 1.28 * questions. 1.29 @@ -23,7 +23,7 @@ 1.30 1.31 /** 1.32 * Tests for conversion of JavaScript arrays to Java arrays and the other 1.33 - * way round. Also generally useful as a JavaScript-to-Java type conversion 1.34 + * way round. Also generally useful as a JavaScript-to-Java type conversion 1.35 * test. 1.36 * 1.37 * @test 1.38 @@ -49,9 +49,9 @@ 1.39 testF(inputValue, type, isNaN) 1.40 } 1.41 1.42 -// Those labeled "Correct?" are not clearly correct conversions. Those 1.43 -// labeled "TypeError maybe?" could actually throw a TypeError, or only 1.44 -// throw a TypeError when in strict mode. 1.45 +// Those labeled "Correct?" are not clearly correct conversions. Those 1.46 +// labeled "TypeError maybe?" could actually throw a TypeError, or only 1.47 +// throw a TypeError when in strict mode. 1.48 // The case of ("false", "boolean") => true is particularly amusing. 1.49 1.50 test(x, "int", 0) // Correct? TypeError maybe?