Philip Chimento

Cool, then I think my advice about JSC still applies, but maybe in reverse; we must both be testing with different versions, and one is newer than the other :smile:...

I've tested again today with JavaScriptCore built from the very latest commit: ``` >>> new Date(2022, 11, 24).toLocaleString('de', {weekday: 'short', day: 'numeric', month: 'long'}) "Sa., 24. Dezember" >>> new Intl.DateTimeFormat('de',...

I'm still pretty sure that must be due to a CLDR update. (https://github.com/tc39/test262/pull/3676 is the recent fallout in test262 due to CLDR 42 using different kinds of spaces than previously.)

I was curious if we had any tests for other features that had been demoted to stage 2, so this motivated me to go clean up the features.txt file: https://github.com/tc39/test262/pull/3782...

I'm not sure I understand the difference - isn't `/(? %%foo%% - %%bar%% :a)/` just as syntactically invalid as `/(?/*{ foo }*/-/*{ bar }*/:a)/`?

After poking at this bug, I think I understand better why you are asking for this. It's simple enough to support `/foo//*{ bar }*/` but without extra work to support...

@rleikis Thanks for your comments. Apologies that I haven't responded sooner. It is true, I don't pay this project much attention anymore and I would welcome if someone else could...

In Python: http://stackoverflow.com/a/22434262/172999

Note, it also messes up the TAP reporter if you print to stdout in a test, since any non-TAP data should be prefixed with `#`.

Thanks for the contribution! I'm a bit mystified though, you are correct that the current references are broken, I see a lot of errors in the Sublime Text console like...