Re: [platform-swt-dev] Cocoa SWT Java 6 64 bit ?

[Steve Northover <Steve_Northover@xxxxxxxxxx>]

If we stick to the (ugly but fast) strategy
we use on Windows and GTK, it should be an "int /*long*/".

Make sure your concerns from the duplicate
bug are captured in the regenerate bindings one, including the "id
constructor".

"Alex Blewitt" <alex.blewitt@xxxxxxxxx>
Sent by: platform-swt-dev-bounces@xxxxxxxxxxx

04/07/2008 02:41 PM

Please respond to
"Eclipse Platform SWT component developers list."        <platform-swt-dev@xxxxxxxxxxx>

To	"Eclipse Platform SWT component developers list." <platform-swt-dev@xxxxxxxxxxx>
cc
Subject	Re: [platform-swt-dev] Cocoa SWT Java 6 64 bit ?

On Mon, Apr 7, 2008 at 4:55 PM, Steve Northover
<Steve_Northover@xxxxxxxxxx> wrote:
>
> Ok, you caught us. We haven't done any work to make the cocoa port
run
> 64-bit.  That normally happens after we have everything running
32-bit.  The
> strategy that we use is a bit tedious (look for /*long*/ in SWT code
on
> Windows and GTK) but in the end, it means that we are optimized at
runtime
> for the architecture.  Given the state of the coca port (a prototype
that we
> are about to ramp up on), the fact that we are not 64-bit happy will
be
> added to the other numerous work items.

Speaking of which ... the cocoa 'id' value uses int in the Java
bindings. Shouldn't that be long?

It would be great if the constructors of the NSxxx objects took an
'id' arg as well as a 'long' arg as that would make casting from one
to another much easier.

Yes, I filed a bug, and yes, it got closed as a duplicate of
'regenerate bindings' but I thought I'd mention the whole int-vs-long
thing here since we were talking 64 bit.

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