I'm really sorry, the mozilla-esr24 url should be:
https://github.com/loongsonhf/ionmonkey-mips
在 2014年2月19日星期三UTC+8下午3时00分41秒，weizhen...@gmail.com写道：
> Hi all,
>
>
>
> We are IonMonkey development team from Loongson Inc, China. We have been
>
> ported IonMonkey of Mozilla-esr24 to ou
Sorry, the mozilla-esr24 code is at:
https://github.com/loongsonhf/loongson-mozilla-central
在 2014年2月19日星期三UTC+8下午3时00分41秒，weizhen...@gmail.com写道：
> Hi all,
>
>
>
> We are IonMonkey development team from Loongson Inc, China. We have been
>
> ported IonMonkey of Mozilla-esr24 to our Loo
Hi all,
We are IonMonkey development team from Loongson Inc, China. We have been
ported IonMonkey of Mozilla-esr24 to our Loongson 3A MIPS platform, which is
available at github:
https://github.com/loongsonhf/loongson-mozilla-central
This job is finished, and IonMonkey works well at our L
On Tue, Feb 18, 2014 at 1:57 AM, Nicolas B. Pierron
wrote:
>
> I think it might make sense to special case the JSFunction class, such as we
> can get the object prototype name in addition to the JSFunction class.
Interesting idea. What's the exact code for getting the object
prototype name from a
On 2/18/14 10:59 AM, David Bruant wrote:
What I meant was "it'd be excellent if Blink and Moz made the
test suite more complete"
Ah, OK.
Yes, that would be a good idea. :)
I guess contributing to the Promise/A+ repo works.
Assuming they care about the subclassing issues and whatnot.
Yes
On Feb 18, 2014, at 11:52 AM, Ehsan Akhgari wrote:
>> The current ES6 consensus needs to be nailed down harder, but I think it
>> will stick. That it isn't compositional won't stop this. Promises were a
>> library de-facto standard from CommonJS and other ecosystems; the
>> committee erred in try
On 2/17/2014, 4:32 PM, Brendan Eich wrote:
The problem is one V8 principal (among others in what I think is a clear
minority) do not agree with the current consensus. The previous
consensus was actually fractured, but no one worked through it and some
amount of miscommunication, perhaps combined
Le 18/02/2014 16:02, Boris Zbarsky a écrit :
On 2/17/14 4:27 PM, David Bruant wrote:
That said, it'd be excellent if Blink and Moz completed the current test
suite (Promise/A+)
Mozilla did, until we just removed cast(). Or at least we passed the
test suite at http://domenic.me/aplus-tests-ag
On 2/17/14 4:32 PM, Brendan Eich wrote:
SpiderMonkey still needs to nativize the DOM/XPCOM-based implementation,
both to follow the spec (including subclassability)
The DOM can easily support subclassability once SpiderMonkey itself
does. The problem is, SpiderMonkey has no subclassing suppor
On 2/17/14 4:27 PM, David Bruant wrote:
That said, it'd be excellent if Blink and Moz completed the current test
suite (Promise/A+)
Mozilla did, until we just removed cast(). Or at least we passed the
test suite at http://domenic.me/aplus-tests-against-the-browser/
sure they implement the
On 02/17/2014 07:30 PM, Jason Orendorff wrote:
On 2/16/14, 11:18 PM, Nicholas Nethercote wrote:
The memory reporting code runs without a |cx|, so in my experimental
code I've just used obj->getClass()->name, and not treated proxies
specially.
Does this sound reasonable?
I think this is the ri
11 matches
Mail list logo
