Path: ...!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.arch Subject: Re: is Vax addressing sane today Date: Tue, 1 Oct 2024 00:33:01 -0000 (UTC) Organization: A noiseless patient Spider Lines: 23 Message-ID: References: <20240930111505.000018a3@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 01 Oct 2024 02:33:01 +0200 (CEST) Injection-Info: dont-email.me; posting-host="45d68bef63035d0f49773effd7a1ab82"; logging-data="2568472"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19kwdK1IgsHwYNkuTI9r8Te" User-Agent: Pan/0.160 (Toresk; ) Cancel-Lock: sha1:B8yQlpEDV1i+i4hAThJVs0t6VPE= Bytes: 2227 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 wrote: > >> Also the fact that those “64-bit” APIs are not entirely “64-bit” ... > > They are entirely 64-bit. : 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.