From: lecoat@atari.org   
      
   Hi MiKRO,   
      
   Miro KropáĠ  
   ek writes:   
   >> I'm afraid if I make that changes, my Eureka 2.12 sources will only   
   >> be compatible with GNU/GCC 4, and not any other C compiler.   
   >   
   > This is not true. On the contrary, most likely you'll discover hidden bugs   
   in your code. And of course the source will stay compatible, as mentioned, the   
   compiler is now more strict but that doesn't mean it doesn't adhere to the C   
   standard.   
   >   
   > So it boils down to the fact whether you're willing to change your code or   
   you're stuck with 3.x forever. Obsolete sources require obsolete compilers.   
      
   Well, I remind you that I'm not supposed to be able to use GNU/GCC 4   
   to build my Eureka 2.12 program. The great advantage with GNU/GCC 3   
   is that it understands my sources, producing warnings that it   
   can tolerates. The other advantage is that it includes 16bits   
   libraries, that are mandatory to build my software, for compatibility   
   with PURE C and furthermore binary compatibility with the ATARI ST.   
      
   Should I abandon the opportunity to build an ATARI ST software to   
   sacrify to the modernity of GNU/GCC 4, because it's new. What   
   improvements does it bring to the m68k-atari-mint target ? I'm   
   suspecting there's more drawbacks than improvements with GNU/GCC 4.   
      
   Why doesn't it include 16bits libs, breaking backward compatibility ?   
      
   Thanks for your answer.   
      
   Best regards,   
      
   --    
   François LE COAT   
   Author of Eureka 2.12 (2D Graph Describer, 3D Modeller)   
   http://eureka.atari.org/   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)