These numbers are from my Shape rooting branch: it has about 200-300
fewer Shape/BaseShape/UnownedBaseShape references than trunk. Exactly
rooting jsscope.* has been slow going because of the rather appalling
state that that code is in.
++
| m-i/js |
++
jsval : 1611
Va
On Nov 26, 2012, at 7:16 AM, Benjamin Peterson wrote:
> 2012/11/26 smaug :
>> I don't see anyone proposing to remove compartments, or anything like that.
>> I'm just hoping to have an API which isn't super error prone.
>
> Do you have specific suggestions or at least any particular pain points?
I
From this thread, it sounds like one problem is that the JSAPI is
requiring users to deal with weird things called "compartments" that
are absolutely meaningless to the calling code. It's JSContexts all
over again. "Why are they needed? What are they for? Can't the engine
just figure it out?" A
On 11/26/2012 03:16 PM, Benjamin Peterson wrote:
2012/11/26 smaug :
I don't see anyone proposing to remove compartments, or anything like that.
I'm just hoping to have an API which isn't super error prone.
Do you have specific suggestions or at least any particular pain points?
The pain point
2012/11/26 smaug :
> I don't see anyone proposing to remove compartments, or anything like that.
> I'm just hoping to have an API which isn't super error prone.
Do you have specific suggestions or at least any particular pain points?
I don't see this thread going anywhere unless someone has ideas
On 11/21/2012 11:29 PM, Jeff Walden wrote:
On 11/21/2012 12:08 PM, Dave Mandelin wrote:
Fair enough. Just out of curiosity, if it didn't have the security benefits,
would you think compartments are worthwhile?
Fixing the leak (the khueyfix to make zombie compartments much harder to
create) d
6 matches
Mail list logo
