Re: JavaScript

Am Dienstag, den 03.07.2012, 20:16 +0200 schrieb "Chris Young"
<chris.young@unsatisfactorysoftware.co.uk>:

>> Vince has committed a change based on your patch.
>
> There seems to be a couple of minor problems though. One is that the
> JS_FS etc macros aren't in the NetSurf headers (I assume this is
> intentional, and they can be easily added to the Spidermonkey
> includes
> in any case)

The JS_FS_ etc. macros were already in my patch. I guess they didn't
made it into the repository
because there wasn't an additional #ifdef JS_VERSION <= 170

So, it's maybe worth a second try.

However, today I tried to build js-1.8 ( all I had found was an rc ).
1.8 is still the same
build system like 1.7, 1.4 etc. so porting it should be absolutely
straight.

The 1,8 rc js-console sadly crashes with an failing assert - this
doesn't happen when build under linux.

So, I still have to stick to js 1.7, except there is an 1.8 release
version around which fixes the bug.
I had a look at the debian squeeze iceweasel patches, but it contains a
lot of them.

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...

Is there anyone with big-endian and working spidermonkey 1.8 jsconsole?
I do not have problems when running
scripts directly, just when starting up the interactive jsconsole. It
happens during JS_NewObjectWithPrototype.

Greets,
Ole