Re: 2 GIG the new 640 MB
- From: Roedy Green <my_email_is_posted_on_my_website@xxxxxxxxxxxxxx>
- Date: Mon, 16 Jan 2006 11:49:11 GMT
On Mon, 16 Jan 2006 00:06:19 -0800, Peter Ammon
<gershwin@xxxxxxxxxxxxxxx> wrote, quoted or indirectly quoted someone
who said :
>But that doesn't mean that Java is automatically "64 bit ready" or ideal
>for 64 bit computers. For example, the length property of an array in
>Java is a 32 bit int even on a 64 bit machine - that means that no Java
>program will ever be able to create an array with more than 4 billion
>elements. Java will need to undergo a transition to 64 bit like any
>other framework out there.
I think that could go very smoothly. From the language level all you
have to do is relax the restriction on using longs in new [ ... ]. You
can continue to use ints even in a 64 bit system.
In the JVM, the new 64 bit array might be implemented with 32-bit or
64-bit code depending on how you allocated it.
the biggest problem is with array.length. Perhaps logically
autocasting it back to int when required. Perhaps there would be two
length commands, one int pseudofield length and a method length() that
gets a long.
It not nearly so frightening as adjusting your pointer arithmetic to
account for different sizes of items.
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
.
- Follow-Ups:
- Re: 2 GIG the new 640 MB
- From: The Ghost In The Machine
- Re: 2 GIG the new 640 MB
- References:
- 2 GIG the new 640 MB
- From: Roedy Green
- Re: 2 GIG the new 640 MB
- From: Peter Ammon
- 2 GIG the new 640 MB
- Prev by Date: Re: 2 GIG the new 640 MB
- Next by Date: Re: 2 GIG the new 640 MB
- Previous by thread: Re: 2 GIG the new 640 MB
- Next by thread: Re: 2 GIG the new 640 MB
- Index(es):
Relevant Pages
|