On Sat, 15 Jan 2011 23:06:51 -0800, Rufus wrote: > Yes - I understand that. After poking around though, I see it's a > matter of rewriting to support being able to run under the Nitro Java
We already use the JIT assembler from Nitro in Jaegermonkey (our method JIT implementation). > engine...which sounds like some syntax verification and a recompile, to > me...dunno, guessing. So back to my first conclusion - a lot of work, > but not "impossible" or "prohibited". > > I'm also left wondering about the difference between Safari for iPad and > Safari under OS X...I'd think they'd be similar, and each use the Nitro > engine...SM runs on OS X already, so how *big* a stretch would it be > *really* to port it to iOS? Nobody's really answered that question as > to level of effort, just put up roadblocks - it ain't "impossible". > > So how hard is it? How many lines of code? Or portions of code? Or > percentage of code? I seriously want to know... It ranges to very very difficult to essentially impossible. A lot of our front end UI code is written in Javascript itself and depend on language quirks and extensions only available in Spidermonkey. New language features tend to appear first in Spidermonkey (Brendan works for Mozilla after all and he invented Javascript). Phil -- Philip Chee <[email protected]>, <[email protected]> http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
