[Mono-list] Mcs bugs fixed (Janet)

Jeroen Janssen japj@xs4all.nl
Thu, 09 Jan 2003 21:17:08 +0100


Andrew Stopford wrote:

>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.
>  
>
Ok, something goes "fundamentally" wrong.
I have a JavaScript test program containing:
----
// Very Simple Test Progra,

writeln("Hello World");
----

Running this through JCommand on MS .NET with csc this results in a C# 
file with
...
// Main program code
public static void GlobalCode()
   {
   Support.Call(globals.Get("writeln"), @"Hello World");
   } // GlobalCode
...

Where the Mono/mcs build & running JCommand produces an empty GlobalCode 
function.
// Main program code
public static void GlobalCode()
   {
   } // GlobalCode

*sigh* I don't have any time for it atm, but I think I need to run this 
through a (mono)debugger to see exactly what's happening.
---
Jeroen