home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.c      Meh, in C you gotta define EVERYTHING      243,242 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 243,175 of 243,242   
   Bart to Keith Thompson   
   Re: printf and time_t   
   06 Feb 26 20:08:57   
   
   From: bc@freeuk.com   
      
   On 06/02/2026 19:21, Keith Thompson wrote:   
   > Bart  writes:   
   >> On 06/02/2026 13:08, Keith Thompson wrote:   
   >>> Bart  writes:   
   >>> [...]   
   >>>> I guess you've never used printf-family functions via the FFI of   
   >>>> another language!   
   >>> As it happens, I haven't.   
   >>> I presume if there were a point, you would have made it by now.   
   >>   
   >> I thought you might have infered it.   
   >>   
   >> All shortcomings of C can apparently be fixed by employing a selection   
   >> of it gcc's 200+ options. So no point in making the language better   
   >> instead.   
   >   
   > Nobody said any of that.   
   >   
   >> But that doesn't work when some bits of raw C need to be used from   
   >> another language. For example, library headers containing a C API,   
   >> which some languages may use as the basis for their own bindings.   
   >   
   > Sure, FFIs can be tricky.   
   >   
   > You randomly introduced FFIs into a discussion of printf formats.  What   
   > irrelevant argument are you going to make next?   
   >   
   > https://en.wikipedia.org/wiki/Gish_gallop   
      
   You seem to have introduced some nonsense of your own.   
      
   I'm simply saying that people discussing here C are often blind to its   
   problems because they employ an advanced C compiler or other analytical   
   tools to mitigate them.   
      
   You can't do that if working with raw C like I do. I've been using C   
   libraries via FFIs and C header files for about 30 years.   
      
   And so, if you want to use *printf functions like that, then the fact   
   that gcc can sometimes report on incorrect format codes is no help at   
   all; I'm not using gcc, /or/ writing C!   
      
   It doesn't help when I'm writing C either, as I either use lesser   
   compilers, or use gcc without any fancy options.   
      
   I believe a language should stand by itself and not rely on complex   
   tooling to make it practical to use. Not even syntax highlighting should   
   be necessary.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca