On Wed, 2007-07-18 at 10:12 +0100, Rupert Smith wrote: > The trouble with generating C# from Java code is that the two > languages follow different conventions. The original .Net was ported > from Java code, basically as a copy over of the Java and then the > minimal amount of work done to turn that into C# that compiles and > works. > > Since then, some very good work by Tomas, has converted the C# code > back into something that is truer to the conventions of C#. In > particular there was no equivalent to javas nio package, which in > combination with the extensions to byte buffers that MINA uses, led to > some horribly designed C# code. So I would like to point out that the > cross porting of Java to C# may not be so simple as you imagine.
I was expecting that Tomas would help us with the code migration and especially with the nio issue. > Do you have a good tool to recomend that cross compiles or converts > Java into C#? or are you talking about 'generating' the C# by hand? I was expecting of using the Java Language Conversion Assistant that comes with visual studio. Another solution would be to use The XML Encoded Source tool that would convert java into XES and XES back to C#. Maybe Tomas knows better tools. > An alternative would be to generate both the Java and the C# from some > sort of language neutral model. That sounds like a lengthy project in > its own right to me... XES would also be a good alternative for our code generation. We can generate XES that would then be transformed into Java or C#. > Personally, I would rather stick with the existing .Net client, and > capitalize on the effort/bug fixing invested in it so far. At least > until someone nullifies that approach by demonstrating a fully working > generation approach. The existing .Net client implements 0.8 and the idea is to migrate it to 0.10 support.
