From: Oliver Buchtala <oliver.buchtala@go...> - 2013-02-03 22:34:25
Am 25.01.2013 20:04, schrieb William S Fulton:
> On 23/01/13 09:02, Eric Wing wrote:
>>> it is under development.
>>> And, it is basically working. Lately, I used it to create a Node.js
>>> Though, it needs improvement. Any collaboration is welcome :)
> Oliver, do you expect patches to fix the problems Eric has outlined,
> or are you able to use Eric's feedback and supply a fix?
>> Hi Oliver,
>> I'm still trying to get things setup on my side (my environment for
>> talking to V8 is complex so I haven't been able to directly run
>> anything real). But with the SWIG V8 code generator, I found a few
>> problems. I was able to work around these by directly modifying the
>> generated output, but I would like to share these issues in hopes that
>> these can be fixed directly in the generator.
>> 1) Don't #include <iostream> unless you really need it. (Android was
>> giving me problems with this…maybe their iostream is broken.) I was
>> able to remove that #include. It doesn't look like anything is using
Of course... there seems to be left some rubbish.
>> All the remaining issues are caused by the differences in C vs C++. I
>> am trying to bind a C module, but it looks like all the V8 stuff
>> requires C++. This has some implications that need to be addressed.
V8 is C++. So I need to force it to generate c++ files.
Thanks. I will consolidate this.
From: Eric Wing <ewmailing@gm...> - 2013-04-09 00:34:15
Hi, I'm starting to look at the V8 backend again.
I'm discovering that the current release of V8 deprecated or removed a
bunch of things that are being used.
For example, these were removed from V8:
The removal of these ultimately breaks these functions/macros:
SWIG_ConvertPtr(obj, ptr, info, flags) SWIG_V8_ConvertPtr(obj, ptr,
#define SWIG_NewPointerObj(ptr, info, flags)
SWIG_V8_NewPointerObj(ptr, info, flags)
#define SWIG_ConvertInstance(obj, pptr, type, flags)
SWIG_V8_ConvertInstancePtr(obj, pptr, type, flags)
#define SWIG_NewInstanceObj(thisvalue, type, flags)
What version/date of V8 is the current backend intended to work with?
And can anybody provide me guidance or hints on how to migrate to the
Beginning iPhone Games Development
From: Oliver Buchtala <Oliver.B<uchtala@jk...> - 2013-04-10 08:42:04
EW> Hi, I'm starting to look at the V8 backend again.
EW> I'm discovering that the current release of V8 deprecated or removed a
EW> bunch of things that are being used.
EW> For example, these were removed from V8:
EW> obj->SetPointerInInternalField(0, cdata);
EW> What version/date of V8 is the current backend intended to work with?
EW> And can anybody provide me guidance or hints on how to migrate to the
EW> current V8?
thanks for this info.
I am using this backend together with node.js current stable version. From the changelog, it seems that v8 of version 18.104.22.168 is used there.
To solve the problem one would have to see how v8 wants the old functions to be replaced... most probably, there will be a new way to wrap blobs (void*).
I can not promise when I am able to address this as I am currently not able to spend time on it.
I put it into my task queue. And of course, if you find out how, it would be great to share with me.