1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
|
/* -*- indent-tabs-mode: nil; js-indent-level: 2 -*- */
/* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
/*
*
* Date: 15 July 2002
* SUMMARY: Testing functions with double-byte names
* See http://bugzilla.mozilla.org/show_bug.cgi?id=58274
*
* Here is a sample of the problem:
*
* js> function f\u02B1 () {}
*
* js> f\u02B1.toSource();
* function f¦() {}
*
* js> f\u02B1.toSource().toSource();
* (new String("function f\xB1() {}"))
*
*
* See how the high-byte information (the 02) has been lost?
* The same thing was happening with the toString() method:
*
* js> f\u02B1.toString();
*
* function f¦() {
* }
*
* js> f\u02B1.toString().toSource();
* (new String("\nfunction f\xB1() {\n}\n"))
*
*/
//-----------------------------------------------------------------------------
var UBound = 0;
var BUGNUMBER = 58274;
var summary = 'Testing functions with double-byte names';
var ERR = 'UNEXPECTED ERROR! \n';
var ERR_MALFORMED_NAME = ERR + 'Could not find function name in: \n\n';
var status = '';
var statusitems = [];
var actual = '';
var actualvalues = [];
var expect= '';
var expectedvalues = [];
var sEval;
var sName;
sEval = "function f\u02B2() {return 42;}";
eval(sEval);
sName = getFunctionName(f\u02B2);
// Test function call -
status = inSection(1);
actual = f\u02B2();
expect = 42;
addThis();
// Test both characters of function name -
status = inSection(2);
actual = sName[0];
expect = sEval[9];
addThis();
status = inSection(3);
actual = sName[1];
expect = sEval[10];
addThis();
sEval = "function f\u02B2\u0AAA () {return 84;}";
eval(sEval);
sName = getFunctionName(f\u02B2\u0AAA);
// Test function call -
status = inSection(4);
actual = f\u02B2\u0AAA();
expect = 84;
addThis();
// Test all three characters of function name -
status = inSection(5);
actual = sName[0];
expect = sEval[9];
addThis();
status = inSection(6);
actual = sName[1];
expect = sEval[10];
addThis();
status = inSection(7);
actual = sName[2];
expect = sEval[11];
addThis();
//-----------------------------------------------------------------------------
test();
//-----------------------------------------------------------------------------
/*
* Goal: test that f.toString() contains the proper function name.
*
* Note, however, f.toString() is implementation-independent. For example,
* it may begin with '\nfunction' instead of 'function'. Therefore we use
* a regexp to make sure we extract the name properly.
*
* Here we assume that f has been defined by means of a function statement,
* and not a function expression (where it wouldn't have to have a name).
*
* Rhino uses a Unicode representation for f.toString(); whereas
* SpiderMonkey uses an ASCII representation, putting escape sequences
* for non-ASCII characters. For example, if a function is called f\u02B1,
* then in Rhino the toString() method will present a 2-character Unicode
* string for its name, whereas SpiderMonkey will present a 7-character
* ASCII string for its name: the string literal 'f\u02B1'.
*
* So we force the lexer to condense the string before using it.
* This will give uniform results in Rhino and SpiderMonkey.
*/
function getFunctionName(f)
{
var s = condenseStr(f.toString());
var re = /\s*function\s+(\S+)\s*\(/;
var arr = s.match(re);
if (!(arr && arr[1]))
return ERR_MALFORMED_NAME + s;
return arr[1];
}
/*
* This function is the opposite of functions like escape(), which take
* Unicode characters and return escape sequences for them. Here, we force
* the lexer to turn escape sequences back into single characters.
*
* Note we can't simply do |eval(str)|, since in practice |str| will be an
* identifier somewhere in the program (e.g. a function name); thus |eval(str)|
* would return the object that the identifier represents: not what we want.
*
* So we surround |str| lexicographically with quotes to force the lexer to
* evaluate it as a string. Have to strip out any linefeeds first, however -
*/
function condenseStr(str)
{
/*
* You won't be able to do the next step if |str| has
* any carriage returns or linefeeds in it. For example:
*
* js> eval("'" + '\nHello' + "'");
* 1: SyntaxError: unterminated string literal:
* 1: '
* 1: ^
*
* So replace them with the empty string -
*/
str = str.replace(/[\r\n]/g, '')
return eval("'" + str + "'");
}
function addThis()
{
statusitems[UBound] = status;
actualvalues[UBound] = actual;
expectedvalues[UBound] = expect;
UBound++;
}
function test()
{
printBugNumber(BUGNUMBER);
printStatus(summary);
for (var i=0; i<UBound; i++)
{
reportCompare(expectedvalues[i], actualvalues[i], statusitems[i]);
}
}
|
