From: Pancho.Jones@proton.me   
      
   On 29/08/2024 10:28, Ahem A Rivet's Shot wrote:   
   > On Thu, 29 Aug 2024 09:32:49 +0100   
   > Richard Kettlewell  wrote:   
   >   
   >> I don’t think I’d fault either decision though the fact that we’ve   
   ended   
   >> up with two conventions does make writing/maintaining portable code a   
   >> bit more annoying,   
   >   
   > 	Portable code should only rely on the standards not   
   > implementations, some very weird possibilities are legal within the   
   > standard.   
   >   
   > 	There are always the int_t types for when size matters.   
   >   
      
   Yes, from what I remember of the 90s, Microsoft code used typedefs,   
   Int32, Int64 or maybe even Macros for types. Big projects sometimes used   
   their own typedefs. I never liked it. I used int and long, but I   
   recognised my code was suboptimal.   
      
   Then I moved to Csharp and Java and stop worrying :-).   
      
   C was shit, for not making types explicit, subsequent OS software   
   developers were just polishing the turd.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)