Hi, As the error is occuring in Janet they only way to try and catch this is to reduce the JS file and then add a section, compile it, if it works add another section etc. This will give us an idea of what is causing the problem and the likely source of the problem within Janet.
As this works ok on mcs this is going to be a Mono bug but until we know what is causing the problem in Janet we won't know what part of Mono it relates to. Cheers Andrew -----Original Message----- From: Jeroen Janssen [mailto:[EMAIL PROTECTED]] Sent: 08 January 2003 22:21 To: Miguel de Icaza Cc: mono-list Subject: Re: [Mono-list] Mcs bugs fixed (Janet) Miguel de Icaza wrote: >Hello, > > > >>>I filed a bug (36321) for what I assume is a mcs bug (sample code is >>>present in the bugreport) >>> >>> >>And another (36323) for another (also sample present). >> >> > >Martin fixed both bugs now. > > Ok, after a (janet) makefile fix it now compiles & links ok under mcs (linux). However, now I got the following error when trying to run JCommand on test.js: japj@debian:~/mono/janet/janet/Test$ mono ./JCommand.exe test.js ParseError at line 136966332, column -1073743544 (byte position 135170044) Message: expected "}" As far as I know, the same code works ok on windows with CSC/.NET Framework. What is the best way to determine the cause of this problem? --- Jeroen _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
