how easy is it to mess with Firefox Javascript interpreter? -


since firefox open source, in theory should possible me hack behavior of interpreter. let's maybe build own profiler, or introduce more fine grained restrictions on javascript behavior , not allow in browser. or something, whatever...

so how easy sort of thing in practice? achieved through sort of plugins? or need recompile interpreter source? or recompile entire browser?

how big interpreter source anyway? hard thing grok has built toy compilers in college?

if restrict interpreter, things not bad. if want deal 2 jits well, it's more work. in terms of codesize, looks we're talking 180k lines of code (headers , c++ files), not counting regexp engine , jits.

understanding interpreter not bad; 1 thing there's bit of documentation @ http://developer.mozilla.org , people on #jsapi channel on irc.mozilla.org happy answer questions.

something profiler need hack source if want profile without perturbing system much. experiments in terms of supported features, want use https://mozillalabs.com/zaphod/ instead, suspect.


Comments

Popular posts from this blog

objective c - Change font of selected text in UITextView -

php - Accessing POST data in Facebook cavas app -

c# - Getting control value when switching a view as part of a multiview -