From: arne@vajhoej.dk   
      
   On 9/22/2025 8:46 PM, Arne Vajhøj wrote:   
   > On 9/22/2025 7:03 PM, Lawrence D’Oliveiro wrote:   
   >> On Mon, 22 Sep 2025 19:57:42 +1200, David Goodwin wrote:   
   >>> Windows 2000 was to introduce new VLM APIs that allow 32bit applications   
   >>> on Alpha to access very large amounts of memory.   
   >>   
   >> There’s a reason the API is still called “Win32”, not “Win64”.   
   Instead of   
   >> using POSIX-style symbolic type names like size_t, time_t and off_t, they   
   >> explicitly use 32-bit types.   
   >>   
   >> This leads to craziness like, when getting the size of a file, it returns   
   >> the high half and low half in separate 32-bit quantities, even on a   
   >> 64-bit   
   >> system, with native 64-bit integer support!   
   >   
   > There are two aspects here.   
   >   
   > 1) types that have different sizes on different   
   >     platforms/compilers/configs vs types that have   
   >     same sizes on all platforms/compilers/configs   
   >   
   > Experience shows that the latter is better than the   
   > former, because it makes it easier to write portable   
   > code with well defined behavior.   
   >   
   > off_t is a signed integer of unknown size.   
      
   On VMS it is 32 or 64 bit depending on whether   
   _LARGEFILE is defined.   
      
   xab.XAB$L_EBK and xab.XAB$W_FFB may not be a pretty   
   interface, but we know we got 32 bit and 16 bit.   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)