C# to Java Conversion? 8
axlrosen asks: "Given Microsoft's current prerelease C# spec, would it be possible to write an automatic converter from C# to Java? Are there any parts of the language that couldn't be converted? Could the 'unsafe' stuff be converted to a combination of Java and C++, using JNI?" Of course something like this is possible, but is it practical at this point? C# is a very new language, and I wouldn't advise starting any serious projects with it until the language has been through its paces. If you are considering between C# and Java for a large project, I'd suggest that you use Java, at least until C# has matured a bit.
Now why would you want to do that? (Score:1)
Given Microsoft's recent track record, good luck even trying to distribute a C# application on anything but the development machine on which it was written.
"There is no C#" (Score:1)
BTW I totally 2nd the poster who comments on how C# is not search-engine compliant. I presume the alternates of C-sharp and Csharp would become the preferred variants for searchable text, but really. I think I'll invent a language and call it
Re:Language wars! (Score:1)
Language wars! (Score:1)
your missing the point of C# (Score:2)
Java is supposed to be cross platforms, but it does not work this way all the time. There are so many different versions of the JDK and they have so many incompatibilities, which Java version would the C# to Java convert to anyway? What would it buy you to convert to Java when there would probably be COM/DCOM or COM+ code in there too?
send flames > /dev/null
Short answer: no. (Score:2)
C# is search engine anti-friendly (Score:3)
I find it especially funny that you can't use "C#" on search.microsoft.com, either.
Why ? (Score:3)
Looking at the language specs, it appears that C# is Microsoft's answer to the in-between language that many Windows programmers have been asking for some time now. There are some projects that don't really need the power (or complexity) of C++, but VB often overdoes it in the effort to oversimplify and kludge everything together.
I welcome an easier way to program COM/DCOM/COM+ on windows platforms - There are times when I require C++ for its speed and control, but I sacrifice developement time to gain this. A middle ground is much needed.
That having been said, why would we need to port a project to java?
I think the question misunderstands the intended domain for the C# language - A COM-based developement environment.
-jerdenn