From: david+usenet@zx.net.nz   
      
   In article <10askk5$2lq0s$4@dont-email.me>, ldo@nz.invalid says...   
   >   
   > 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.   
      
   On 64bit Windows, pointers that Win32 APIs consume are all 64bit. The   
   API wasn't renamed because it wasn't really a useful thing to do - while   
   the underlying types may have changed, the API was still largely the   
   same. Building the same code for both 32bit and 64bit Windows is easy   
   enough.   
      
   > 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 is a good reason for this: Windows NT gained support for large   
   files before Unix did. The very first release of Windows NT in 1993   
   supported files larger than 4GB, but Microsofts compiler at the time   
   didn't support 64bit integers so a different solution was required.   
      
   Other oddities in the Win32 API are usually explained by a desire to   
   make porting applications from Win16 as easy as possible.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)