MacArthur, Ian (SELEX GALILEO, UK) wrote:
> That said, we do have 64-bit apps with 32-bit GUI's that seem to work
> OK, so I'm not sure how much of an issue it really is - have we really
> reached the stage where we need 64-bit spaces for our GUI's these days?
Oddly, I don't know much about the details of this subject wrt OSX.
My understanding with OSX is that currently (Leopard 10.5 and older)
all apps are 32bit, and thus limited to 4G, but the kernel can
address full 64bits.
So the kernel can run 32bit apps, assigning each a 32bit
chunk of the whole 64bit arena. So multiple 32bit apps can
be running using their entire 32bit space without overlapping,
but the apps can't address more than that.
With Snow Leopard (10.6), the entire OS is true 64bit, so kernel
and apps can address 64bit data. And that's useful for folks
with huge datasets (3d cgi folks, terrain mapping, med imaging, etc).
What I don't know is if one were to compile an FLTK app for 64bits
under OSX, does any of our code need to be made 64bit aware in
order to communicate with the 64bit native APIs?
We've surely gone through this with linux, sgi, and windows 64bit,
with OSX being the last to the plate.
I think Matt and Mike are probably our resident experts on the
OSX native APIs that FLTK uses.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
