Subj : Re: What changed with JS prototype usage?
To   : netscape.public.mozilla.jseng
From : Peter Wilson
Date : Mon Dec 13 2004 11:26 am

Brendan Eich wrote:
> Peter Wilson wrote:
> 
>> I have tried a small test file using this idiom and everything works 
>> fine.
>> There must be something in my file which is quietly choking the parser.
>> I need to cut the file down and add back pieces incrementally to find 
>> the problem. I'll let you know if I find anything.
> 
> 
> If you JS_SetErrorReporter(cx, ...) before compiling using cx, you 
> should see the error(s).
> 
> /be
I've found it.

The following code in the js file prolog caused all the problems:

const xaFILE_FileTransportService =
Components.classes["@mozilla.org/network/file-transport-service;1"].
	getService(Components.interfaces.nsIFileTransportService);

It turns out that nsIFileTransportService is now obsolete. However, this 
shouldn't cause the system to become unstable without any hint of an 
error. As I'm working from an XUL page I'm not sure how your advise 
about JS_SetErrorReporter can be applied. Isn't the console window this 
by default?

.