Eclipse Community Forums: C / C++ IDE (CDT) » Why 64bit Eclipse version

Home » Language IDEs » C / C++ IDE (CDT) » Why 64bit Eclipse version

Why 64bit Eclipse version [message #186023]

Mon, 26 February 2007 08:32

Eclipse User

Originally posted by: fwein.lse.eei.uni-erlangen.de

Hi,

I hope, I'm not too off-topic:

Why is there a eclipse download for a 64bit jre?

Is the codebase different?
Is an optimized compiler-switch used?

This messes up with my compile once, run anywhere picture and I'm just
curious.

Thanks,

Fabian

Re: Why 64bit Eclipse version [message #186079 is a reply to message #186023]

Mon, 26 February 2007 12:32

Eclipse User

Originally posted by: dschaefer.qnx.com

Fabian Wein wrote:
> Hi,
>
> I hope, I'm not too off-topic:
>
> Why is there a eclipse download for a 64bit jre?
>
> Is the codebase different?
> Is an optimized compiler-switch used?
>
> This messes up with my compile once, run anywhere picture and I'm just
> curious.
>
> Thanks,
>
> Fabian

Interesting question. The reason for the different downloads is that
Eclipse has a number of native libraries, starting with SWT. The CDT has
a native library for process management and Windows registry access as well.

Now Eclipse is 99% Java so we do get a lot of the benefits of compile
once, run anywhere, but that 1% is probably what makes Eclipse such a
high quality environment. I lived through the pain of IDEs written in
Swing. Eclipse performs like most desktop apps because SWT is mainly C code.

Just my opinion, though.
Doug

Re: Why 64bit Eclipse version [message #186143 is a reply to message #186079]

Tue, 27 February 2007 03:57

Eclipse User

Originally posted by: fwein.lse.eei.uni-erlangen.de

>> Why is there a eclipse download for a 64bit jre?

> Now Eclipse is 99% Java so we do get a lot of the benefits of compile
> once, run anywhere, but that 1% is probably what makes Eclipse such a
> high quality environment. I lived through the pain of IDEs written in
> Swing. Eclipse performs like most desktop apps because SWT is mainly C
> code.

Thanks for the answer! I guess this is also the reason for the versions
of Together. I found writing webapps in JSP much more convenient than in
Swing - but writing AWT applets in the old times when the IE had an old
JRE was really a pain in the back.

Regards,

Fabian

Previous Topic:	"Broken Pipe" error when compiling on Fedora Core
Next Topic:	Filtering files with extentions

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Sep 03 05:41:35 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter