SungchulCho / v8-juice

Automatically exported from code.google.com/p/v8-juice
Other
0 stars 0 forks source link

cvv8 is broken? #35

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
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

Original issue reported on code.google.com by kreuzerk...@gmail.com on 23 Dec 2013 at 6:54

GoogleCodeExporter commented 8 years ago
oh, never mind... saw the "ACHTUNG" on the homepage

Original comment by kreuzerk...@gmail.com on 23 Dec 2013 at 6:57

GoogleCodeExporter commented 8 years ago
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. :(

Original comment by sgbeal@googlemail.com on 23 Dec 2013 at 9:30

GoogleCodeExporter commented 8 years ago
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... 

Original comment by kreuzerk...@gmail.com on 23 Dec 2013 at 7:20

GoogleCodeExporter commented 8 years ago
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.

Original comment by sgbeal@googlemail.com on 23 Dec 2013 at 7:26

GoogleCodeExporter commented 8 years ago
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 :(

Original comment by kreuzerk...@gmail.com on 23 Dec 2013 at 8:09

GoogleCodeExporter commented 8 years ago
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. :(

Original comment by sgbeal@googlemail.com on 23 Dec 2013 at 8:51

GoogleCodeExporter commented 8 years ago
yep, saw your post, guess if no one picked it up yet, it is not gonna happen...

Original comment by kreuzerk...@gmail.com on 23 Dec 2013 at 8:58