Following the lead of Blink in setting the web platform guidelines, we on
the V8 team came up with a similar set of guidelines specific to V8. They
are available at https://devsite.googleplex.com/v8/launchprocess.
We hope this document will make our decision-making process even more open
and
Not transparent quite yet - that link is not public and there is no
summary. ;)
☆*PhistucK*
On Mon, Sep 16, 2013 at 12:41 PM, Dmitry Lomov dslo...@chromium.org wrote:
Following the lead of Blink in setting the web platform guidelines, we on
the V8 team came up with a similar set of
NaCl/PNaCl are sep projects. they would run their own guidelines
independently of Chromium.
-mike
On Mon, Sep 16, 2013 at 11:28 AM, PhistucK phist...@gmail.com wrote:
Yes, however, Chromium brings in PNaCl to the web platform. Chromium
brings in VP8 with alpha support to the web platform.
I am not talking about NaCl/PNaCl specifically, those were merely examples.
So this is most certainly relevant within this context. You turned it into
a NaCl/PNaCl oriented discussion. And frankly, it does not really matter if
it is standardized or not, it is not the issue at hand.
Chromium is the
Yes, however, Chromium brings in PNaCl to the web platform. Chromium brings
in VP8 with alpha support to the web platform. Chromium brings in VP9
support to the web platform.
So while it is mostly a chrome around the web platform, it has its control
as well, which is why those public service
which isn't relevant. if you want to talk about standardization of the
NaCl/PNaCl projects, then you should start threads on the relevant
NaCl/PNaCl mailing lists.
-mike
On Mon, Sep 16, 2013 at 11:32 AM, PhistucK phist...@gmail.com wrote:
Right, but Chromium exposes them to the web platform,
So with the resent changes to Persistent how can we store a series of
PersistentFunction handles to an STL container like map ?
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google
Yes, I know, but this is what I'm asking about - does anyone could get it
out from the deep inside of v8 and make use of it?
In other worlds, what needs to be done to instantiate v8's parser object,
run parsing and achieve AST? Any examples of the code?
I really need that, and I need that
Shouldn't the use of Handle and Local be interchangeable ?
Has it been decided which of the two will be depreciated in the end ?
It seems that we cannot assign a Handle value to the Eternal and we need
to use Local instead ...
--
--
v8-users mailing list
v8-users@googlegroups.com
This doesn't build on Windows. Anyone else seeing this? I'm getting lots
of errors related to inconsistent dll linkage and when building all the v8
stuff, not my stuff. With a few modifications to v8 source, it now works.
But, I don't think you'll want my changes!
-J
--
--
v8-users mailing
Doesn't build on mac either...
Ld ../xcodebuild/Debug/lineprocessor normal x86_64
cd
/Users/jacquave/dev/animal/sandboxes/jacquave/v1/shared/third_party/v8/samples
setenv MACOSX_DEPLOYMENT_TARGET 10.5
/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-g++-4.2 -arch
I started using this:
template typename T struct PersistentP : public
boost::shared_ptrv8::PersistentT
{
typedef boost::shared_ptrv8::PersistentT _inherited;
PersistentP(v8::PersistentT *inPersistentP0 = NULL) {
_inherited::reset(inPersistentP0);
}
v8::LocalT GetLocal() const {
return
Maybe look at something like tiny-js which has a much simpler codebase (
https://code.google.com/p/tiny-js/).
-L
On Monday, September 16, 2013, Ivan P. wrote:
Yes, I know, but this is what I'm asking about - does anyone could get it
out from the deep inside of v8 and make use of it?
In other
13 matches
Mail list logo
