|
Please document JSAPI changes in SpiderMonkey 24 release notes, going forward
|
| |
If you make changes to JSAPI, please note them in the draft 24 release notes, just cloned from the 17 release notes:
[link]
It shouldn't be too hard to keep up with documentation, as long as we keep up with them as we go. Please do so!
24 notes won't be perfect, as 17 notes weren't (and kind of in some ways didn't exist, even), but if we start keeping everything documented as we go, 24 will be better, and 31 will be even better yet.... more »
|
|
|
Funny fuzzer bugs
|
| |
[link] recently got filed as a fuzz bug discovered by the fuzzers, in which they stumbled across internal, totally-unsafe (when misused) functionality and hilarity ensued. It occurs to me that this isn't the first time that we've had fuzzers report amusingly hilarious bugs, and it's moderately fun to look back on these things and wonder when the fuzzers will achieve sentience. I'm going to start tagging them as [fuzzer-lulz] in the status whiteboard; feel free to tag any other such bugs you encounter. The criteria for tagging are vague and fuzzy (pun intended), but who cares. :-)... more »
|
|
|
Retiring JavaScript versions
|
| |
Hi,
I've been thinking about Dave Herman's comment one the generator bug [1] for a couple of days. Specifically:
"The explicit versioning is Mozilla-specific, and is basically a failed experiment; the overwhelming majority of the web doesn't use it. The HTML5 zeitgeist and the "One JavaScript" (1JS) movement, meanwhile, have... more »
|
|
|
Internationalization API enabled in standalone builds now, clobber times will increase a bit
|
| |
With bug 866305 landed, the shell build by default now includes the Intl object, and the existing toLocale*String methods all use Intl functionality to work. Yay!
But this also means that building now requires building ICU as well. Not so yay. That adds several minutes to compile time (for me, with a -j8 build and some inadvertent ccaching I forgot to turn off), a several-x increase in overall compile time.... more »
|
|
|
Can JS_EncodeScript be used to protect the source code ?
|
| |
Hi,
We are using JS / SpiderMonkey VM / C++ to ship games for mobile devices (ios/android).
What we want to do is to "protect" the JavaScript source code.
Currently we are using JS_EncodeScript / JS_DecodeScript to protect it. So, instead of shipping the JS files, we are shipping the "encoded scripts" instead.... more »
|
|
|
Tweak to SpiderMonkey's #include rules
|
| |
Hi all,
In [link], Luke
(module owner) endorsed a slight change to the rules for #include
ordering in SpiderMonkey.
The new rule is that in a jsfoo.cpp file, the jsfoo.h header should be
the first header #included in the file. (Simliarly, in foo/Bar.cpp,... more »
|
|
|
Project Ideas
|
| |
Hi,
My name is Wei Wu and I would like to participate in Mozilla during GSoC
2013 as a student. I have been studying IonMonkey for several days, but I
haven't found any related ideas about it on Mozilla's idea list
pages[1][2]. The following are some ideas I'm interested in and I want to
know your opinions/comments:... more »
|
|
|
Long-running compilation steps
|
| |
Hi,
For [link] I'm interested
in adding more checks of SpiderMonkey's operation callback in
potentially long-running operations. For example, when running the
asm.js Unreal demo, parsing takes several seconds, so in my patch I
added a check after the parsing of each statement.... more »
|
|
|
