XPost: comp.os.linux.misc, alt.folklore.computers   
   From: bowman@montana.com   
      
   On Wed, 7 Jan 2026 13:30:14 +0100, Carlos E.R. wrote:   
      
   > On 2026-01-06 19:57, Charlie Gibbs wrote:   
   >> On 2026-01-06, Lars Poulsen  wrote:   
   >>   
   >>> On 2026-01-06, Carlos E.R.  wrote:   
   >>>   
   >>>> My C teacher said it was a mistake to use C as an all purpose   
   >>>> language, like for userland applications. Using C is the cause of   
   >>>> many bugs that a proper language would catch.   
   >>>>   
   >>>> That was around 1991.   
   >>>>   
   >>>> He knew. He participated in some study tasked by the Canadian   
   >>>> government to study C compilers, but he could not talk about what   
   >>>> they wrote.   
   >>   
   >> What language(s) did he suggest instead?   
   >   
   > I don't remember if he did. Maybe he told samples, but I think he mostly   
   > told us of quirks of the language, things that were errors, but that the   
   > compiler did not signal, so that we being aware we would write correct C   
   > code.   
   >   
   > It is possible that current C compilers signal many more problems that   
   > back then, but not runtime errors.   
      
   gcc has become pickier. That isn't always a welcome thing when working   
   with legacy code and requires a search of the compiler options to get it   
   to shut up about such horrible heresies as assuming a function returns an   
   int.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)