C # has a few more features besides Java. Take delegates, for example: many very simple C # applications use delegates, while people from Java indicate that the observer pattern was sufficient. Thus, in order for a tool to convert a C # application that delegates use, it would have to transfer the structure from using delegates to the implementation of the observer pattern. Another problem is that C # methods are not virtual by default, while Java methods. In addition, Java has no way to make methods non-virtual. This creates another problem: a C # application can use the behavior of a non-virtual method through polymorphism, since it does not translate directly to Java. If you look around, you will probably find that there are many tools for converting Java to C #, since it is a simpler language (please do not flame me, I did not say what I said easier); however, you will find very few if any decent tools that convert C # to Java.
I would recommend changing your approach to converting from Java to C #, as it will create fewer headaches in the long run. Recently, Db4Objects have released their internal tool that they use to convert Db4o to C # to the public. This is called Sharpen. If you register on your site, you can view this link with instructions for using Sharpen: http://developer.db4o.com/Resources/view.aspx/Reference/Sharpen/How_To_Setup_Sharpen
(I was registered with them for a while, and they do not like spam)
Lorentz Sep 17 '08 at 1:57 2008-09-17 01:57
source share