Sujet : Re: is Vax addressing sane today
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.archDate : 01. Oct 2024, 01:33:01
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vdffvs$2ec8o$3@dont-email.me>
References : 1 2 3 4
User-Agent : Pan/0.160 (Toresk; )
On Mon, 30 Sep 2024 11:15:05 +0300, Michael S wrote:
On Mon, 30 Sep 2024 01:28:42 -0000 (UTC)
Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
Also the fact that those “64-bit” APIs are not entirely “64-bit” ...
They are entirely 64-bit.
<
https://arstechnica.com/gadgets/2018/05/microsoft-learn-from-apple-ii/2/>:
Another example; Win32 has a function for getting the size of a
file. File sizes on Windows are limited to 2^64 bytes, and so they
need a 64-bit integer to be expressed easily. But the API call to
get the size of a file doesn't give you a 64-bit value. Instead,
it gives you a pair of 32-bit values that have to be combined in a
particular way. For 32-bit Windows, that's sort of understandable;
32-bit Windows is, well, 32-bit, so you might not expect to be
able to use 64-bit integers. But if you use the same API in 64-bit
Windows, it still gives you the pair of numbers, rather than just
a nice simple 64-bit number. While this made some kind of sense on
32-bit Windows, it makes no sense at all on 64-bit Windows, since
64-bit Windows can, by definition, use 64-bit numbers.