We don't have a good mechanism for this but I think we should have. It would make v8 much more useful as a stand-alone javascript implementation if we had a model for loading libraries, for instance like python's site-packages. I've also noticed that several other projects have implemented their own basic javascript libraries, file i/o for instance, and it would be great if there were some basic libraries available so everyone didn't have to write their own.
Unfortunately this is not a high priority for us -- we're focusing on v8 as a component of Google Chrome and this just wouldn't be useful in that context. So while you may see something like this eventually it probably won't be any time soon. -- Christian On Sat, Feb 21, 2009 at 5:30 PM, Joe Antoon <[email protected]> wrote: > > Is there a standard plugin format I can access from my stand-alone v8 > code? > > I've noticed a lot of interesting add-ons like llv8call or k7, but > they all seem a little heavyweight for me. I'm not entirely > comfortable mixing my main code with a dozen C++ wrapper extensions at > compile-time, and I'd rather have something I can compile separately > and drop-in as a binary. I can see "v8ext" in llv8call, but is there > a lot of support for that? > > For my own code, I pass a global object to a "load" function in a > shared library from a single "import" function which looks for .so > and .js files in a lib folder. It would be great if there were a > repository of plug-ins in a similar fashion. > > > > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
