A few days back I raised a bug with Railo - "Bug with scoping inside iterator functions" (RAILO-3000) - which only happens on one of my Railo installs (out of six installs, on four different machines). Micha can't replicate it either. I'm trying to get to the bottom of what's going on, and what's different about my install.
Update:
I've got to the bottom of this. See "Railo: I've got to the bottom of that code I asked you to test for me"Here's the code:
On my machine at work, this outputs:
1
1
1
1
1
2
3
4
On all my Railo instances at home, it outputs:
1
2
3
4
1
2
3
4
And this is what Micha gets too. All my instances are fully patched to 4.2.0.006.
I've just run this code on cflive.net, and - whaddya know... it displays the buggy behaviour too. So that's a relief: there is a bug, and it's not down to weirdness on my machine.
I tried to run it on trycf.com (that's a link straight to the Gist... that is cool) and the code gives a bogus error:
Error:
key [ITERATIONS] doesn't exist on line 10
Which is obviously nonsense. I'll hit-up Abram about that one. If, however, I exit on the line about that, it runs the first loop correctly, outputting 1,2,3,4.
Anyway, can you please try running that code on your Railo install, and lemme know which version of the output you see (and if you see the bung version, what exact version / install type / platform your Railo install is)? Cheers.
Oh yeah, and my environment is various Windows versions:
- 7 Starter 32-bit, Railo Express
- 7 Home Premium 64-bit, Railo Express
- 7 (not sure of flavour: probably Professional or Enterprise) 64-bit, Railo Express (this is the one showing the buggy behaviour)
- 8 Standard 64-bit, both Railo on Tomcat and Railo Express
--
Adam
