From: news-1326478115@discworld.dascon.de   
      
   On 2015-10-04, Francois LE COAT  wrote:   
   >   
   > Well, the same recipe should at least give the same meal.   
      
   Not if the recipy is unclear, like "take a spoonful of whatever red   
   ingredient you find in the fridge".   
      
   > What should I think about GNU/GCC 4 compared to GNU/GCC 2 and 3,   
   > PURE C 1.1 and other compilers, building my C program Eureka 2.12,   
   > when the produced binary is such a messy meal ?   
      
   That your source is a messy meal, when judged by the current C standards   
   that the compiler implements - for good reason (it gives much better   
   performance when compiling standard-compliant sources). And no, the compiler   
   is working as expected (by the standard) - it it giving you one kind of   
   correct result, just not the one you want.   
      
   If you insist on keeping your source code as it is, you are limited to old,   
   badly-optimizing compilers that will by chance get the results you want.   
      
   Otherwise, you need to take a look *where* the problems are (as I said,   
   compiling with full warnings enabled, understanding and removing them is a   
   good start, but deeper debugging may be required). The links I posted should   
   provide a good start to understand what constructs are to be avoided when   
   using modern compilers.   
      
   cu   
   Michael   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)