On Jan 24, 2008 6:37 PM, Justin Perkins <[EMAIL PROTECTED]> wrote: > > On Jan 24, 2008 1:09 PM, dashifen <[EMAIL PROTECTED]> wrote: > > > > That's been my experience as well. Hanging commas just seem to cause > > problems for IE from which it (a) doesn't recover and (b) doesn't tell > > you about. > > A hanging comma will cause trouble for Safari as well, it's classified > as a warning in the ECMA spec, which puts it on the same level as a > missing semicolon, though obviously one causes real problems and one > is harmless. > > I've grown in the habit of immediately looking for a hanging comma > when weird errors appear in IE and not Firefox. There are JavaScript > syntax checkers to catch this type of stuff for you. Andrew Dupont > wrote one a while ago for TextMate, it's saved me on more than one > occasion.
As you, when there are weird errors only in IE I look for this immediately, and most of the time it's the case. And a simple single regular expression does the trick with no need for external tools :) In textmate, find ,(\s*}) and replace for $1 That regexp will surely work in Aptana or your favorite flavor of eclipse :) Best, -Nicolas > -justin > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
