Question : Royal Flush Browser Test

I wrote a JavaScript program to calculate poker statistics for fun. When it came time to find out how often a Royal Flush can occur, I ran it IE8 RC1, but I would nearly always get an exception when dealing 60,000 hands or so (see code snippet bottom comment).

So I tried the program in Google Chrome 2.0.166.1, and time after time there was no problem at all. It performs the best compared to all other browsers.

After a short analysis, it seems that IE8 RC1 is writing values to arrays which are then passed to the "hand" function in my code, and then losing the data in the arrays somehow ... the array items become undefined values.

What gives?

PS: Royal Flush seems to occur once in every 4000 hands dealt on average. As long as you don't fold of course.

Code Snippet:

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:
190:
191:
192:
193:
194:
195:
196:
197:
198:
199:
200:
201:
202:
203:
204:
205:
206:
207:
208:
209:
210:
211:
212:
213:
214:
215:
216:
217:
218:
219:
220:
221:
222:
223:
224:
225:
226:
227:
228:
229:
230:
231:
232:
233:
234:
235:
236:
237:
238:
239:
240:
241:
242:
243:
244:
245:
246:
247:
248:
249:
250:
251:
252:
253:
254:
255:
256:
257:
258:
259:
260:
261:
262:
263:
264:
265:
266:
267:
268:
269:
270:
271:
272:
273:
274:
275:
276:
277:
278:
279:
280:
281:
282:
283:
284:
285:
286:
287:
288:
289:
290:
291:
292:
293:
294:
295:
296:
297:
298:
299:
300:
301:
302:
303:
304:
305:
306:
307:
308:
309:
310:
311:
312:
313:
314:
315:
316:
317:
318:
319:
320:
321:
322:
323:
324:
325:
326:
327:
328:
329:
330:
331:
332:
333:
334:
335:
336:
337:
338:
339:

Open in New Window

Select All

Answer : Royal Flush Browser Test

Interesting that 131,072 is 2^17 - it looks like I hit the maximum value for 16-bit integer (or something).

If that is the case, then I'd say there are no problems passing arrays anymore in IE8.

I tested in IE8 ver 8.0.6001.18702

Question : Royal Flush Browser Test

Answer : Royal Flush Browser Test

Interesting that 131,072 is 2^17 - it looks like I hit the maximum value for 16-bit integer (or something).If that is the case, then I'd say there are no problems passing arrays anymore in IE8.I tested in IE8 ver 8.0.6001.18702

Interesting that 131,072 is 2^17 - it looks like I hit the maximum value for 16-bit integer (or something).

If that is the case, then I'd say there are no problems passing arrays anymore in IE8.

I tested in IE8 ver 8.0.6001.18702