Re: [platform-swt-dev] Why different Java code for 32 and 64 bit SWT ver

[Bogdan Gheorghe <gheorghe@xxxxxxxxxx>]

Hi Stephen -

The initial versions of SWT all ran
on 32-bit with 64-bit support being added at a later date. While there
is no technical reason why you couldn't use long for both 32 and 64, at
the time we were optimizing for the majority (which was the 32 bit case).
We always strive to be as close to the running platform as possible for
efficiency sake.

- B

From:	Stephan Aßmus <superstippi@xxxxxx>
To:	"Eclipse Platform SWT component developers list." <platform-swt-dev@xxxxxxxxxxx>
Date:	12/12/2012 07:00 AM
Subject:	[platform-swt-dev] Why different Java code for 32 and 64 bit SWT        versions?
Sent by:	platform-swt-dev-bounces@xxxxxxxxxxx

---

Hi again,

a quick google search didn't turn up anything enlightening…

Is there a simple technical reason why there need to be two versions of
the *Java* code for SWT depending on the 32 or 64 bit version? I have written
my own native library and simply used "long" where I need to
store pointers in Java code. While I compile either a 32-Bit or 64-Bit
version of the native library, the library API can be the same and I have
to only maintain one version of the Java code. Is there something in SWT
that makes this approach impossible?

Best regards,
-Stephan

_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev