Subj : Re: Proposed Update to the JavaScript Test Library
To   : netscape.public.mozilla.jseng
From : Martin Honnen
Date : Mon Feb 07 2005 05:38 pm



Bob Clary wrote:


> The new e4x tests result in 4 errors when run online in a Mozilla trunk
> build. I have not been able to compare the new vs. old results for the
> shell tests for e4x since I have been unable to build a JavaScript or
> XPConnect shell that supports e4x. Any instructions on how to build an
> e4x capable JavaScript or XPConnect shell would be appreciated.

When I have a js.exe here on Windows, sources pulled via CVS, built with 
cygwin make but using MS VC, there is a function named options defined 
in the shell and after executing
options('xml')
in the shell it suddenly understands XML literals (E4X stuff like
var god = <god>Kibo</god>;
).
I have also tried options('xml') in an xpcshell but that shell doesn't 
know a function named options.

You can also directly run the js shell in "E4X mode" by calling it as
   js.exe -x
at least that works with the shell I have here, it indicates the -x as a 
command line argument when it prints its usage and the source
   <http://lxr.mozilla.org/mozilla/source/js/src/js.c#435>
indeed suggests that then the 'xml' option is switched on.




-- 

	Martin Honnen
	http://JavaScript.FAQTs.com/

.