最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

Modifying V8 JavaScript Engine provided with Chrome - Stack Overflow

matteradmin4PV0评论

I want support for a new API that is normally not supported by V8 JS Engine provided with Chrome. Is it possible to do this by tweaking V8 provided with Chrome.

I'm open to using Spidermonkey which is provided with Firefox. I just want this API to be supported by a popular browser.

I tried looking for an answer on Google forums and here but most of them talk about embedding V8.

I want support for a new API that is normally not supported by V8 JS Engine provided with Chrome. Is it possible to do this by tweaking V8 provided with Chrome.

I'm open to using Spidermonkey which is provided with Firefox. I just want this API to be supported by a popular browser.

I tried looking for an answer on Google forums and here but most of them talk about embedding V8.

Share Improve this question asked Aug 25, 2011 at 21:49 TheZelusTheZelus 4706 silver badges19 bronze badges 1
  • You could modify v8, pile, then try embedding in webkit, which is a close relative to chrome than spidermonkey – HyderA Commented Aug 25, 2011 at 21:53
Add a ment  | 

1 Answer 1

Reset to default 8

Just a thought...

For example, a V8 developer may wish to checkout the V8 trunk alongside a stable version of Chromium. So, they might setup a .gclient file like so:

 solutions = [   
 { 
     "name"        : "chrome",
     "url"         : "http://src.chromium/svn/trunk/src/chrome@5000",
     "custom_deps" : {
       "v8" : "http://v8.googlecode./svn/trunk"
     }   
}]

http://www.chromium/developers/how-tos/chromium-modularization

You could perhaps pile Chromium with your own version of v8 by pointing the custom_deps for v8 to it.

Post a comment

comment list (0)

  1. No comments so far