views:

11

answers:

0

Hello,

I use the Bigloo 3.3a version. I am currently working on running Bigloo scheme functions (compiled into .class) from Eclipse by calling the functions from a java class. I follow the following steps: Take a .scm file with possibly several functions defined in it. populate it into a package structure. Compile these files into either a library or a .class file. import the above in Eclipse. write a java main class where these functions are accessed.
Manage the necessary conversions in data type during the interaction between the Java and the Bigloo classes. Currently, most of the bigloo inbuilt functions seem to be working fine in this procedure.

The problem is when I use the function "open-input-file". When I try opening a file using this function in the scheme file, I come across 2 scenarios: I compile it on the command line with the command bigloo -jvm -o file.jvm file.scm and run it with the ./file.jvm cmd, it executes properly giving the expected output. I compile it on the command line with the same command, include the generated class file in Eclipse application and run, it gives me the java.lang.NullpointException error and points the error to the line 894 of rutime/Ieee/port.scm in the function (open-input-file string #!optional (bufinfo #t)). Also, when I try to use the functions of the library ssax-sxml from eclipse, it ends up with the same 2 scenarios as above.

I am curious as to how can running the same class file in the Java environment provide 2 different behaviors. Is there some specific version of JDK or Eclipse I need to use? Also I'd be glad if you could direct me towards which .zip of the bigloo (bigloo_s, bigloo_u) do i import of the ssax-sxml library.