<snip>
> > So, finally I want to suggest that you also try to compile 1.7, it
> > would be better if we both
> > use the same "old" version. 1.7 should be easy to port. At least as
> > easy as 1.5. Then
> > we don't have to figure out difference between 1.5 and 1.7...
>
> I'll give it a try when I get time - might not be for a couple of
> weeks though. Unfortunately it wasn't me who ported 1.5 so I'm not
> exactly wure what was changed to get it to work.
>From a recent commit looks like you moved up to 1.7. Just a quick
query, does 1.7 not include jsversion.h when you pull in mozjs/js.h
because you seem to be overriding JS_VERSION and if teh library sets
it for you that would seem counterproductive.
I have not yet merged any of the pre 1.8.0 version jsapi.h macro
changes as I beleive as I continue to add functionality I will be
breaking them :-/ As an observation I do not have easy development
acess to library version other than 1.8.0 and 1.8.5
And just in case you had not twigged what the mozilla guys were up to,
basically the method calls have been altered 1.7 -> 1.8.0 -> 1.8.5 to
make them consistant in signature with the property callbacks.
To do this they introduced the JS_* macros but certianly in 1.8.0
these appear to not work properly for native calls which is why i
introduced our own JSAPI wrappers which attempt to use macro magic to
make the netsurf jsapi code version agnoisic.
Hope some of this helps.
--
Regards Vincent
http://www.kyllikki.org/
No comments:
Post a Comment