Comments on: More ES5 backwards-incompatible changes: regular expressions now evaluate to a new object, not the same object, each time they’re encountered http://whereswalden.com/2010/01/15/more-es5-incompatible-changes-regular-expressions-now-evaluate-to-a-new-object-not-the-same-object-each-time-theyre-encountered/ Mozilla, politics, economics, law, backpacking, cycling, and other random desiderata Sat, 19 Jun 2010 05:15:45 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Wandering Dude http://whereswalden.com/2010/01/15/more-es5-incompatible-changes-regular-expressions-now-evaluate-to-a-new-object-not-the-same-object-each-time-theyre-encountered/comment-page-1/#comment-147697 Wandering Dude Fri, 21 May 2010 18:49:19 +0000 http://whereswalden.com/?p=1265#comment-147697 Thanks so much for this incredibly useful information. I ran into the exact situation you described with a validation routine. It worked as expected in Internet Explorer, but not so in Firefox. You saved me a lot of confusion over the strange behavior the code was exhibiting. Thanks so much for this incredibly useful information. I ran into the exact situation you described with a validation routine. It worked as expected in Internet Explorer, but not so in Firefox.

You saved me a lot of confusion over the strange behavior the code was exhibiting.

]]> By: What the JavaScript RegExp API Got Wrong, and How to Fix It http://whereswalden.com/2010/01/15/more-es5-incompatible-changes-regular-expressions-now-evaluate-to-a-new-object-not-the-same-object-each-time-theyre-encountered/comment-page-1/#comment-140303 What the JavaScript RegExp API Got Wrong, and How to Fix It Mon, 01 Mar 2010 08:43:45 +0000 http://whereswalden.com/?p=1265#comment-140303 [...] nonintuitive behavior, but Firefox (and later Google Chrome) did, and as a result it became the second most duplicated JavaScript bug report for Mozilla. Fortunately, ES5 got rid of this rule, and now regex literals [...] [...] nonintuitive behavior, but Firefox (and later Google Chrome) did, and as a result it became the second most duplicated JavaScript bug report for Mozilla. Fortunately, ES5 got rid of this rule, and now regex literals [...]

]]> By: Hallvord R. M. Steen http://whereswalden.com/2010/01/15/more-es5-incompatible-changes-regular-expressions-now-evaluate-to-a-new-object-not-the-same-object-each-time-theyre-encountered/comment-page-1/#comment-139482 Hallvord R. M. Steen Mon, 25 Jan 2010 14:57:25 +0000 http://whereswalden.com/?p=1265#comment-139482 I know Opera implemented this per ES3 but I don't remember off the top of my head how long that implementation lasted.. Just like Mozilla, we have a number of bug reports against the ES3 behaviour. I know Opera implemented this per ES3 but I don’t remember off the top of my head how long that implementation lasted.. Just like Mozilla, we have a number of bug reports against the ES3 behaviour.

]]> By: Jeff http://whereswalden.com/2010/01/15/more-es5-incompatible-changes-regular-expressions-now-evaluate-to-a-new-object-not-the-same-object-each-time-theyre-encountered/comment-page-1/#comment-139319 Jeff Sat, 16 Jan 2010 19:00:29 +0000 http://whereswalden.com/?p=1265#comment-139319 I'm not sure I understand the question. If you're going to iterate through a string, you should make sure to use a new regular expression each time you do so. This suggests that global regular expressions probably shouldn't be defined at top level outside of loops. However, if you do define it that way but don't use the regular expression after you're done iterating, you should be fine. I’m not sure I understand the question. If you’re going to iterate through a string, you should make sure to use a new regular expression each time you do so. This suggests that global regular expressions probably shouldn’t be defined at top level outside of loops. However, if you do define it that way but don’t use the regular expression after you’re done iterating, you should be fine.

]]> By: Neil http://whereswalden.com/2010/01/15/more-es5-incompatible-changes-regular-expressions-now-evaluate-to-a-new-object-not-the-same-object-each-time-theyre-encountered/comment-page-1/#comment-139315 Neil Sat, 16 Jan 2010 10:44:36 +0000 http://whereswalden.com/?p=1265#comment-139315 So, the correct way to iterate over a global regexp is to save it in a variable first? So, the correct way to iterate over a global regexp is to save it in a variable first?

]]> By: Jeff http://whereswalden.com/2010/01/15/more-es5-incompatible-changes-regular-expressions-now-evaluate-to-a-new-object-not-the-same-object-each-time-theyre-encountered/comment-page-1/#comment-139303 Jeff Fri, 15 Jan 2010 20:53:01 +0000 http://whereswalden.com/?p=1265#comment-139303 Oops, yes, retitled. Oops, yes, retitled.

]]> By: Dorus http://whereswalden.com/2010/01/15/more-es5-incompatible-changes-regular-expressions-now-evaluate-to-a-new-object-not-the-same-object-each-time-theyre-encountered/comment-page-1/#comment-139297 Dorus Fri, 15 Jan 2010 19:01:17 +0000 http://whereswalden.com/?p=1265#comment-139297 Your title confuses me a bit, don't you mean either 'ES3 incompatible' or 'ES5 compatible'? Your title confuses me a bit, don’t you mean either ‘ES3 incompatible’ or ‘ES5 compatible’?

]]>