INTL 3:770/1 3:770/3   
   REPLYADDR steveo@eircom.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID: <20240901115314.3d7795351c717fa546c0f6dc@eircom.net> b40e69c4   
   REPLY:  70fea57e   
   PID: SoupGate-Win32 v1.05   
   On Sun, 1 Sep 2024 11:07:17 +0100   
   mm0fmf  wrote:   
      
   > On 01/09/2024 08:50, Lawrence D'Oliveiro wrote:   
   > > On Thu, 29 Aug 2024 21:33:28 +0100, druck wrote:   
   > >   
   > >> Yes stdint.h is your friend   
   > >   
   > > Unless you have an elderly code base that still hasn’t caught up with   
   > > C99 ...   
   >   
   > Or you were programming in C on an Analog Devices SHARC were char was 32   
   > bits.   
      
   	I'll bet that broke a lot of bad code :)   
      
   	Stll even in that environment a compliant compiler should still   
   provide int_t types. They'd probably have to have horrendously   
   inefficient implementations not dissimilar to the bitfields in structs but   
   they should exist. Woe betide anyone who thought they could put a char into   
   an int16_t safely though.   
      
   --   
   Steve O'Hara-Smith   
   Odds and Ends at http://www.sohara.org/   
   For forms of government let fools contest   
   Whate're is best administered is best - Alexander Pope   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 129/305 153/757   
   SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426   
   SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100   
   SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426