refaadventure.blogg.se - Firefox esr 38.2.1 download

#Firefox esr 38.2.1 download Patch
#Firefox esr 38.2.1 download code

Additionally, they don't go through the hassle of bundling a version that was first released more than a year before.Īlso the sm52 release looks less complete than our a23 one, only a pre-release package.Īre you talking about the size of the bundle? sm45 was abnormaly big, so sm52 and 60 look tiny in comparison. But we cannot wait for that moment, because then we would not be able to report bugs. SM also receives regular small updates during the lifetime of a release, so it would only make sense for them to fully release once the version has reached end-of-life.

#Firefox esr 38.2.1 download Patch

We often need to patch SM against bugs that only affect embedders, and not Firefox, and those bugs are not quickly fixed. On the Wikipedia page, one can find the list of releases I'm speaking about, as well as other embedders that can be consulted (some of them embed all the versions, not just the released ones).Ībout releases not being nicely released: given the low number of embedders, SpiderMonkey does not have very robust standalone release scripts. This commit explicitly shows that the previous version they used was 52. Other projects who embed SpiderMonkey confirm that this is the correct list of releases: most notably GNOME, who migrated from SM52 to SM60 in this issue. On their IRC, one can find a link to, which looks like an attempt at a new format of the documentation for the embedders this repo does describe SM60 as the current release. This information was confirmed by the SM maintainers on IRC. Those dates are taken from : SM releases match the releases of Firefox ESR, as stated in the documentation. SM60 started to be developed on, was released, and will receive fixes until (two versions after the release of SM68). However, I confirm the past released versions of SM were 38, 45 and 52. Knowing about these things beforehand may increase the platforms 0ad can run on, so it may be worth to explore (or describe if already explored).Ībout the ESR versions of SpiderMonkey: yes the documentation is poorly maintained, and releases of SpiderMonkey are not well announced (more on that below). you mentioned somewhere to plan to go to sm60 after sm52, but I still didn't see any information that indicates that sm60 is planned as a release

#Firefox esr 38.2.1 download code

That changes our code behavior, but this is ES6-compliant as far as I understood. I chose to follow the same convention as the SM developers, which is to return true when there is a failure.

Mark shared memory in direct access operations ( JS_GetUint16ArrayData and JS_GetUint8ArrayData).

Remove compile'n go ( setCompileAndGo).

Remove JSCLASS_CACHED_PROTO_WIDTH workaround in our code.

Array functions (such as JS_IsArrayObject) are fallible and output to params.

JS::Evaluate now takes scope chains explicitly Use the oppoertunity to improve the ErrorReporter.

Remove JS::RuntimeOptionsRef.varObjFix.

Add js/Initialization.h to source/scriptinterface/ScriptEngine.h.

Removal of obsolete spidermonkey patches in patch.sh. In particular, removed the NSPR dependency on Unix.

Here is the list of changes, for eased review: