Issue 35 in v8-juice: cvv8 is broken?

[v8-j...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 35 by kreuzerk...@gmail.com: cvv8 is broken?
http://code.google.com/p/v8-juice/issues/detail?id=35

What steps will reproduce the problem?
1.Take latest v8
2.Take latest cvv8
3.Try to compile your program with latest changes applied

cvv8 compilation will fail since v8 does not have Arguments class anymore



--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[v8-j...@googlecode.com]

Comment #1 on issue 35 by kreuzerk...@gmail.com: cvv8 is broken?
http://code.google.com/p/v8-juice/issues/detail?id=35

oh, never mind... saw the "ACHTUNG" on the homepage

[v8-j...@googlecode.com]

Comment #2 on issue 35 by sgb...@googlemail.com: cvv8 is broken?
http://code.google.com/p/v8-juice/issues/detail?id=35

Yes, unfortunately nobody has stepped up to take over the project, and i no
longer have the patience and energy to deal with Google's continual
changing of the public APIs. :(

[v8-j...@googlecode.com]

Comment #3 on issue 35 by kreuzerk...@gmail.com: cvv8 is broken?
http://code.google.com/p/v8-juice/issues/detail?id=35

I understand your decision. google doing a favour to everyone when sharing
these libraries, but, no commitments, live with it or leave it. that's the
major reason I don't like em as open source...
BTW, any suggestion for replacement library? checked the vu8 - last commit
a year ago, I guess it is broken too...

[v8-j...@googlecode.com]

Comment #4 on issue 35 by sgb...@googlemail.com: cvv8 is broken?
http://code.google.com/p/v8-juice/issues/detail?id=35

i would recommend vu8, but as you saw, it also hasn't been updated (since
long before the v8 breakage, apparently). The v8 changes broke every single
client of v8. The Chromium team (the core v8 target) required "months of
porting" (according to one of the Chromium devs) to accommodate the new
API, so i suspect that very few add-libs like cvv8 and vu8 survived the
apocalypse. i read somewhere that the node.js team was struggling with the
porting effort, but they have a relatively large community of developers,
whereas vu8 and cvv8 were basically one-person operations.

[v8-j...@googlecode.com]

Comment #5 on issue 35 by kreuzerk...@gmail.com: cvv8 is broken?
http://code.google.com/p/v8-juice/issues/detail?id=35

Checked the node.js today... they don't have the stuff I need (at least I
don't see it in the API) - STL wrappers for V8
now we stuck with old V8 and I don't see how we can upgrade to the newer
one until someone comes and writes new wrapper library...
Sad story, indeed :(

[v8-j...@googlecode.com]

Comment #6 on issue 35 by sgb...@googlemail.com: cvv8 is broken?
http://code.google.com/p/v8-juice/issues/detail?id=35

i have offered to hand over cvv8 to anyone who wants to put in the effort
of making it work with (today's flavour of) v8, but that hasn't happened
yet. :(

[v8-j...@googlecode.com]

Comment #7 on issue 35 by kreuzerk...@gmail.com: cvv8 is broken?
http://code.google.com/p/v8-juice/issues/detail?id=35

yep, saw your post, guess if no one picked it up yet, it is not gonna
happen...