Hello, So, seems that I've finished exception support in my project. At least some basic tests that I've written behave quite well. It appeared that the old code that used 'sys->rescue' and 'sys->raise' is quite easy to adapt to the new exception handling scheme. As of exceptions are done, seems that all core features of translator and jvm itself are working. Everything else is just fixing and implementing Java Class Library classes and system support functions.
I need better testing of everything though, I'm thinking of porting some huge framework to see how it works. Next week I'm going to play more with my project. To write some more tests (I think, filesystem manipulations and network are next), to test some pieces of code from the Internet. Also to work on debugging support, as Inferno is really bad in debugging dis bytecode, so we need sbl files and java source code display support in wm/deb. I also have some interesting thoughts about the real-life usage of these things. Currently any java class file needs to be translated to be used. We may write some ClassLoader class, that would do that automatically. Or even we can unpack jar files and translate everything we find there, so that there will be minimal amount of work to run existing java apps in Inferno. Or we could write jarfs (or javafs), that will provide union fs in place of jar file, with all the classes converted. This will be like more 'Inferno-way'. I'm just excited with endless possibilities of Inferno with Java support! -- Regards, Dmitry Kabak -- You received this message because you are subscribed to the Google Groups "Plan 9 Google Summer of Code" group. To unsubscribe from this group and stop receiving emails from it, send an email to plan9-gsoc+unsubscr...@googlegroups.com. To post to this group, send email to plan9-gsoc@googlegroups.com. Visit this group at http://groups.google.com/group/plan9-gsoc. For more options, visit https://groups.google.com/groups/opt_out.
