I've updated this changelist. Now the javascript code from within d8.cc
is factored out into d8.js and the natives infrastructure has been
changed to allow several generated natives files.
http://codereview.chromium.org/7519
--~--~-~--~~~---~--~~
v8-dev mailing l
Did you upload a new patch set using gcl upload?
On Tue, Oct 21, 2008 at 9:26 AM, <[EMAIL PROTECTED]> wrote:
> I've updated this changelist. Now the javascript code from within d8.cc
> is factored out into d8.js and the natives infrastructure has been
> changed to allow several generated native
LGTM. I guess the next step is to start using d8 to run our tests
instead of the shell sample. Is there anything we could remove from the
shell sample once d8 is alive and kicking?
http://codereview.chromium.org/7519/diff/401/605
File src/d8.h (right):
http://codereview.chromium.org/7519/diff/4
If d8 is going to become the defacto shell for v8, I'd like to request
that argument handling be setup to be more compatible with other
JavaScript shells (namely, SpiderMonkey & Rhino). Issue 39 addresses
this for the old shell.
--~--~-~--~~~---~--~~
v8-dev mailing
I don't know exactly what we want our primary shell to be, the shell
sample or d8, but I agree that we should support passing command-line
arguments through d8 to scripts.
On Tue, Oct 28, 2008 at 6:35 PM, Louis P. Santillan <[EMAIL PROTECTED]> wrote:
>
> If d8 is going to become the defacto shell
