Closed GoogleCodeExporter closed 9 years ago
changing to high priority
Original comment by steve.ye...@gmail.com
on 19 Apr 2008 at 10:38
This would be much appreciated. I've currently got a number of Firefox
extensions
that use 1.8 features extensively.
Original comment by dougkearns@gmail.com
on 27 Sep 2008 at 4:18
Related to this, when developing inside of Mozilla chrome, if would be nice if
js2-mode would handle ifdef directives. Should I file an issue for this?
Example:
#ifdef XP_WIN
#expand aExecutable.leafName != "__MOZ_APP_NAME__.exe";
#else
#ifdef XP_MACOSX
#expand aExecutable.leafName != "__MOZ_APP_DISPLAYNAME__.app";
#else
#expand aExecutable.leafName != "__MOZ_APP_NAME__-bin";
#endif
#endif
regards,
David
Original comment by davidld...@gmail.com
on 8 Jan 2009 at 6:57
That's an entirely different bug, so should be filed separately.
Original comment by bsmedb...@gmail.com
on 8 Jan 2009 at 7:01
I've implemented sufficient logic to cause things to not explode on JS 1.8
expression
closures in my hgimportsvn'd hg repo if anyone wants a stopgap solution.
changeset:
http://hg.mozilla.org/users/bugmail_asutherland.org/opc-js2-mode/rev/a3d10dfbbb8
2
repo:
http://hg.mozilla.org/users/bugmail_asutherland.org/opc-js2-mode/
Original comment by sombr...@gmail.com
on 10 Jul 2009 at 5:59
Fixed in 20090723.
Original comment by steve.ye...@gmail.com
on 23 Jul 2009 at 10:36
Original issue reported on code.google.com by
steve.ye...@gmail.com
on 19 Apr 2008 at 10:12