From: alex.buell@munted.eu   
      
   On Thu, 2024-08-22 at 19:18 +0000, Charlie Gibbs wrote:   
   > > > FAR and NEAR specifiers used with JMP   
   > >    
   > >  	The obscenity was these qualifiers making their way into C   
   > > source   
   > > code - try writing (or even reading) the declaration for a near   
   > > pointer to a function returning a far pointer to an array of   
   > > functions returning near pointers to integers.   
   > >    
   > >  	Then realise that you *alos* wanted this source code to be   
   > > portable.   
   >    
   > A bloody pain in the ass, all of it.  Forget the 640K barrier -   
   > I was much more concerned with the 64K barrier.  I wound up   
   > writing pointer normalization routines and all sorts of other   
   > hacks to handle large tables - and still keep it compatible   
   > with *n*x.  I only recently stripped out all that crap.   
   > Good riddance.   
      
   Huge pointers for code + data for up to 1MB, oh the Ghods, much slower   
   than using using tiny pointers limited to 64KB segments. But yes,   
   playing games with segment registers and splitting data into 64KB   
   segments was significantly quicker and generated smaller binaries.    
   --    
   Tactical Nuclear Kittens   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)