 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Java Forum / General / March 2007Which would be the most-used java compiler in the industry?
Would it be fair to say that it is javac? > Would it be fair to say that it is javac? Absolutely. jikes is a niche. The IBM, BEA and Oracle ones are mostly used for big production boxes not so much for development. Arne For IBM's JDK, the compiler also called javac, just another implementation. But if you are dealing with some IBM's products such as Websphere or something, you must have the IBM's JDK(in some cases, there is a special edition for Websphere) as your development base, as there're some differences between IBM's and Sun's > > Would it be fair to say that it is javac? > [quoted text clipped - 6 lines] > > Arne > For IBM's JDK, the compiler also called javac, just another > implementation. But if you are dealing with some IBM's products such > as Websphere or something, you must have the IBM's JDK(in some cases, > there is a special edition for Websphere) as your development base, as > there're some differences between IBM's and Sun's WAS requires IBM JDK to run. But the code you write should hopefully compile fine with a SUN javac. Arne > WAS requires IBM JDK to run. > > But the code you write should hopefully compile > fine with a SUN javac. That's kind of creepy: WAS is only source-compatible, not bytecode-compatible? -- Adam Maass >> WAS requires IBM JDK to run. >> [quoted text clipped - 3 lines] > That's kind of creepy: WAS is only source-compatible, not > bytecode-compatible? The IBM JVM is fully byte compatible. It is a either a library issue or a support issue. Arne Not exactly, it depends on which version of Sun JVM you used to compile. IBM's WAS JDK only compatible with Sun JDK 1.4x. But in this version also some constant are not exactly same with sun's. I can't remember which constants, something relative to jar package schema. > >> WAS requires IBM JDK to run. > [quoted text clipped - 9 lines] > > Arne > Not exactly, it depends on which version of Sun JVM you used to > compile. IBM's WAS JDK only compatible with Sun JDK 1.4x. But in this > version also some constant are not exactly same with sun's. I can't > remember which constants, something relative to jar package schema. I find it very questionable whether any IBM Java is only compatible with SUN Java 1.4.x. IBM Java is certified as being J2SE compliant, so if a *documented* features does not work, then you should ask IBM to fix it. If it is *undocumented*, then ... Arne > > For IBM's JDK, the compiler also called javac, just another > > implementation. But if you are dealing with some IBM's products such [quoted text clipped - 8 lines] > > Arne I was under the impression that WAS uses the IBM JDK on some platforms and not on others. I think on Solaris WAS uses the SUN JDK. http://frustrationsofaprogrammer.blogspot.com/ >>> For IBM's JDK, the compiler also called javac, just another >>> implementation. But if you are dealing with some IBM's products such [quoted text clipped - 8 lines] > I was under the impression that WAS uses the IBM JDK on some platforms > and not on others. I think on Solaris WAS uses the SUN JDK. Sounds likely since I don't think that IBM JDK exist for Solaris. Arne Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.