Home » Language IDEs » Java Development Tools (JDT) » Eclipse inner heart?
| Eclipse inner heart? [message #72642] |
Thu, 03 July 2003 20:58  |
Eclipse User |
|
|
|
Originally posted by: umdougmm.hotmail.com
I remeber reading somewhere that Eclipse comes with its own sdk for java
development (meaning, its own IBM JIT compiler etc...). Is this true?
And if so, can one change the compiler and run-time used by eclipse when
developing java software? Also, if this is indeed true, and if eclipse
does not use the 'javac' and 'java' that it points to, what run-time
does it use to render itself? Is that what the sun sdk/jre is needed
for? To run eclipse, and then eclipse uses the IBM compiler and
run-time for java software development? This would certainly seem a
little amusing to me if true....
Doug
|
|
| | |
| Re: Eclipse inner heart? [message #72943 is a reply to message #72642] |
Fri, 04 July 2003 14:20  |
| Eclipse User |
|
|
|
Originally posted by: burner.zclipse.org
On Thu, 03 Jul 2003 19:58:09 -0500, Doug wrote:
> I remeber reading somewhere that Eclipse comes with its own sdk for java
> development (meaning, its own IBM JIT compiler etc...). Is this true?
> And if so, can one change the compiler and run-time used by eclipse when
> developing java software? Also, if this is indeed true, and if eclipse
> does not use the 'javac' and 'java' that it points to, what run-time
> does it use to render itself? Is that what the sun sdk/jre is needed
> for? To run eclipse, and then eclipse uses the IBM compiler and
> run-time for java software development? This would certainly seem a
> little amusing to me if true....
There are a number of misconceptions hear that need to be cleared up. And
it comes down to an understanding of the difference between a source
compiler and a JIT compiler.
Eclipse comes with (as mentioned in another reply) a .java -> .class
compiler. This has nothing to do with IBM's JIT compiler that comes with
IBM's JRE/JDK and is NOT included with Eclipse.
The incremental compiler that it built into Eclipse is deeply integrated
with the Java editor and provides many of the major features that Eclipse
users enjoy.
Of course, you can always drop to the command line and run your own
compiler on the source files, but why would you want to?
Certainly, you can define an ant build process and use any compiler that
ant supports, but why would you want to have to wait for ant to run every
time you save a file?
Eclipse, since it is written in Java, requires a JVM to be able to
execute. An SDK is not needed unless you want to use ant's default javac
task.
As you can see, there are two types of compilers for Java. One converts
the .java file to the .class file. Examples of this are javac, jikes,
Eclipse's integrated compiler. The other compiler is the JIT, which is
deeply integrated into the JVM. Sun's Hotspot compiler an example of a
JIT.
> Doug
mike
|
|
|
| Re: Eclipse inner heart? [message #72960 is a reply to message #72943] |
Fri, 04 July 2003 15:05 |
| Eclipse User |
|
|
|
Originally posted by: umdougmm.hotmail.com
Michael R Head wrote:
> On Thu, 03 Jul 2003 19:58:09 -0500, Doug wrote:
>
>
>>I remeber reading somewhere that Eclipse comes with its own sdk for java
>>development (meaning, its own IBM JIT compiler etc...). Is this true?
>>And if so, can one change the compiler and run-time used by eclipse when
>>developing java software? Also, if this is indeed true, and if eclipse
>>does not use the 'javac' and 'java' that it points to, what run-time
>>does it use to render itself? Is that what the sun sdk/jre is needed
>>for? To run eclipse, and then eclipse uses the IBM compiler and
>>run-time for java software development? This would certainly seem a
>>little amusing to me if true....
>
>
> There are a number of misconceptions hear that need to be cleared up. And
> it comes down to an understanding of the difference between a source
> compiler and a JIT compiler.
>
> Eclipse comes with (as mentioned in another reply) a .java -> .class
> compiler. This has nothing to do with IBM's JIT compiler that comes with
> IBM's JRE/JDK and is NOT included with Eclipse.
>
> The incremental compiler that it built into Eclipse is deeply integrated
> with the Java editor and provides many of the major features that Eclipse
> users enjoy.
>
> Of course, you can always drop to the command line and run your own
> compiler on the source files, but why would you want to?
>
> Certainly, you can define an ant build process and use any compiler that
> ant supports, but why would you want to have to wait for ant to run every
> time you save a file?
>
> Eclipse, since it is written in Java, requires a JVM to be able to
> execute. An SDK is not needed unless you want to use ant's default javac
> task.
>
> As you can see, there are two types of compilers for Java. One converts
> the .java file to the .class file. Examples of this are javac, jikes,
> Eclipse's integrated compiler. The other compiler is the JIT, which is
> deeply integrated into the JVM. Sun's Hotspot compiler an example of a
> JIT.
>
>
>>Doug
>
>
> mike
Ah, pardon. I should not have put the JIT in the first line. And since
someone mentioned that the bundled compiler with eclipse adds features
to eclipse, the question would be: What sorts of features can it add
thanks to bundling its own compiler that it couldn't have provided the
users with had eclipse presented users with the opportuinity to choose
the java compiler?
Doug
|
|
|
| Re: Eclipse inner heart? [message #72979 is a reply to message #72960] |
Fri, 04 July 2003 15:20 |
| Eclipse User |
|
|
|
Originally posted by: burner.zclipse.org
On Fri, 04 Jul 2003 14:05:15 -0500, Doug wrote:
>> mike
> Ah, pardon. I should not have put the JIT in the first line. And since
> someone mentioned that the bundled compiler with eclipse adds features
> to eclipse, the question would be: What sorts of features can it add
> thanks to bundling its own compiler that it couldn't have provided the
> users with had eclipse presented users with the opportuinity to choose
> the java compiler?
Basically, it can do all the things that eclipse does. That is, Eclipse
can 'understand' all the details of the language you're using, it can know
there's going to be an error before an actual compile takes place, it can
add all the additional style warnings that it does ...
The Eclipse compiler is fully compliant with the language, so why do you
want to use a different compiler?
Granted, it would be nice to be able to try out the new JDK1.5 features,
but, that's really a different language and does require new code to
support it in the IDE anyway.
> Doug
mike
|
|
|
| Re: Eclipse inner heart? [message #73030 is a reply to message #72979] |
Fri, 04 July 2003 20:25 |
| Eclipse User |
|
|
|
Originally posted by: umdougmm.hotmail.com
Michael R Head wrote:
> On Fri, 04 Jul 2003 14:05:15 -0500, Doug wrote:
>
>
>>>mike
>>
>>Ah, pardon. I should not have put the JIT in the first line. And since
>>someone mentioned that the bundled compiler with eclipse adds features
>>to eclipse, the question would be: What sorts of features can it add
>>thanks to bundling its own compiler that it couldn't have provided the
>>users with had eclipse presented users with the opportuinity to choose
>>the java compiler?
>
>
> Basically, it can do all the things that eclipse does. That is, Eclipse
> can 'understand' all the details of the language you're using, it can know
> there's going to be an error before an actual compile takes place, it can
> add all the additional style warnings that it does ...
>
> The Eclipse compiler is fully compliant with the language, so why do you
> want to use a different compiler?
>
> Granted, it would be nice to be able to try out the new JDK1.5 features,
> but, that's really a different language and does require new code to
> support it in the IDE anyway.
>
>
>>Doug
>
>
> mike
Well, I hate to say this, but JB8 EE does all the things you mentioned
above and makes use of the java sdk you specify in the jb settings
|
|
|
| Re: Eclipse inner heart? [message #73105 is a reply to message #73030] |
Sat, 05 July 2003 02:13 |
| Eclipse User |
|
|
|
Originally posted by: burner.zclipse.org
On Fri, 04 Jul 2003 19:25:54 -0500, Doug wrote:
> Well, I hate to say this, but JB8 EE does all the things you mentioned
> above and makes use of the java sdk you specify in the jb settings
Eclipse also lets you choose whichever JRE/SDK you want in its settings.
But this is different from allowing you to choose the compiler you want to
use at development/debug time. Indeed, Eclipse doesn't even require an
SDK, it can even run with just a 1.3 compatible JRE (due to the fact that
it does include its own compiler).
It should also be noted that Eclipse has excellent support for ant, which
itself allows any compiler to be used for compilation during full builds.
Really, the only reason I can see for using a particular compiler is for
building deployment artifacts. Since Eclipse supports this via ant, I
don't see what the point of Eclipse natively supporting all the different
javac and jikes versions for development time compilation.
Again, the Eclipse compiler is fully compliant with the language, so why
do you want to use a different compiler?
mike
|
|
|
Goto Forum:
Current Time: Thu Jul 24 11:15:48 EDT 2025
Powered by FUDForum. Page generated in 0.14175 seconds |
Home