Re: .net to Java plugin (Re: 11 Reasons Why .NET Will Fail)
"Roy Schestowitz" <newsgroups@xxxxxxxxxxxxxxx> wrote in message
__/ [ Oliver Wong ] on Tuesday 09 May 2006 15:08 \__
"asj" <kalim1998@xxxxxxxxx> wrote in message
Here's a new plugin to convert all dem C# apps to Java:
I took a look at it, and it seems to require a mapping from the .NET
library to the J2SE API library. Unfortunately, sometimes there doesn't
exist a one-to-one mapping between a class in one library to the other.
page doesn't explain what it plans to do to handle those cases.
I.e. the easy parts are done, but the hard parts aren't even
which causes me to lack confidence in this project.
I was once assigned the task of finding C++ to Java convertors and, from
I can recall, it was too complex to become practical. Let me try to find a
thread which is relevant...
So, without much manual work, this is less than feasible, let alone
(or programmatic to use a pun). The scale of the existing C++ library
this a /huge/ project.
Right, but the OP was about C# to Java, not C++ to Java. The former is
actually quite easy, from a syntactical point of view. It's just that
converting API calls, as you've said, is a huge project.
On the other hand, when you said "the .NET API", people have a more or
less good idea of what library you're talking about. My understanding is
that with C++, there is no "one standard library".