JS1.8, to ship as part of Gecko 1.9, will be a smaller change from JS1.7 than 1.7 was from 1.6. But there are a few things we want to fix in 1.7 to track ES4/JS2, and a few more things from ES4 to implement and field-test: - generator expressions - JSON encoder and decoder - slice syntax - more and better array extras (see bug 363040) - generalized destructuring for-in (bug 366941) Missing dependency bugs coming soon. /be

Also: - generator.close() automation only for a generator started by a for-in construct This will simplify the GC, but require JSOP_ENDITER emulation by JSOP_SETSP so that close is automated when exiting a for-in due to an exception. /be

mrbkap, please propose bugs that we didn't fix for js1.7 (that one where let bindings turn into var bindings at top level, e.g.). /be

how about bug 238324?

(In reply to comment #3) > how about bug 238324? That looks at a glance to be entirely outside of the core language and engine -- is it? Core language features such as packages should wait for JS2 on Tamarin (ActionMonkey), which will start development very soon but take longer than JS1.8. JS1.8 needs to be wrapped up pretty quickly. /be

(In reply to comment #0) > - JSON encoder and decoder That's bug 340987.

(In reply to comment #1) > Also: > > - generator.close() automation only for a generator started by a for-in > construct Finally a sensible thing to do that would remove all that crazy stuff about close phase and its scheduling. > > This will simplify the GC, but require JSOP_ENDITER emulation by JSOP_SETSP so > that close is automated when exiting a for-in due to an exception. This is bug 349326. I will try to implement it based on bug 379758 comment 1 during this week.

Related (I think): can/should we make JS1.8 the default for XUL-loaded JS in Gecko 1.9? We didn't in 1.8.1 for good compatibility reasons, but it makes for a lot of poking around by extension and app authors to get the right versioning parameters, and I think we'd do better by them in 1.9 to make the switch.

(In reply to comment #7) > Related (I think): can/should we make JS1.8 the default for XUL-loaded JS in > Gecko 1.9? We didn't in 1.8.1 for good compatibility reasons, but it makes for > a lot of poking around by extension and app authors to get the right versioning > parameters, and I think we'd do better by them in 1.9 to make the switch. Please file that bug and make it block this one? /be

(In reply to comment #6) > (In reply to comment #1) > > Also: > > > > - generator.close() automation only for a generator started by a for-in > > construct > > Finally a sensible thing to do that would remove all that crazy stuff about > close phase and its scheduling. Yes, JS1.7 followed Python too far there. Sorry about that. > > This will simplify the GC, but require JSOP_ENDITER emulation by JSOP_SETSP so > > that close is automated when exiting a for-in due to an exception. > > This is bug 349326. I will try to implement it based on bug 379758 comment 1 > during this week. Do you want to rip out the close phase in the same bug? /be

(In reply to comment #9) > > This is bug 349326. I will try to implement it based on bug 379758 comment 1 > > during this week. > > Do you want to rip out the close phase in the same bug? No. I prefer not to mix the patches implementing different things.

(In reply to comment #10) > No. I prefer not to mix the patches implementing different things. Sounds good -- would you please file that bug and make it block this one? Thanks, /be

(In reply to comment #11) > > would you please file that bug and make it block this one? See bug 380469.

(In reply to comment #7) > Related (I think): can/should we make JS1.8 the default for XUL-loaded JS in > Gecko 1.9? Filed bug 381031.

We want to ban indirect eval, except for w.eval where w is a window object. Is there a bug on file already? I'm not sure we can pull this off before Mozilla 2, but it's worth considering. /be

See bug 382509.

This bug should be closed soon. A doc-js1.8 bug may still be needed. Opinions? /be

I'll be tackling docs, I've already made some good headway: http://developer.mozilla.org/en/docs/New_in_JavaScript_1.8 I'll go back through the recently-closed tickets and make sure everything lands in there. The tracking bug for doc-js1.8 is bug 421027.

Waldo, you going to get to bug 416636 soon? /be

Any updates on this? It would be nice to have a current SpiderMonkey release, with all the performance improvements that are in Fx3.

Dirkjan, for the source release, see bug 428420, which has quite a few blocking bugs, including some ugly crashes (that don't affect Firefox).

I moved the dependencies from bug 428420 to here.

reverting changes made in comment 21 due to bug 428420 comment 5.

1.8 is out. This bug should probably be closed and any depends-on bugs moved to a new tracker. /be

I'm going to resolve this -- I think bug 421027 is resolved too, just not yet marked resolved. /be