From: tr.17687@z991.linuxsc.com   
      
   scott@slp53.sl.home (Scott Lurndal) writes:   
      
   > Tim Rentsch  writes:   
   >   
   >> "James Russell Kuyper Jr."  writes:   
   >>   
   >>> On 2026-01-07 08:06, Tim Rentsch wrote:   
   >>>   
   >>>> scott@slp53.sl.home (Scott Lurndal) writes:   
   >>>>   
   >>>>> Michael S  writes:   
   >>>>>   
   >>>>>> On Tue, 6 Jan 2026 10:31:41 -0500   
   >>>>>> James Kuyper  wrote:   
   >>>>>>   
   >>>>>>> If you know that an expression has one of the standard-named   
   >>>>>>> types or typedefs for with there is a corresponding printf()   
   >>>>>>> specifier, you should use that specifier.  Otherwise, if you   
   >>>>>>> know that an expression has one of the types declared in   
   >>>>>>> , you should use the corresponding macro #defined in   
   >>>>>>>  to print it.   
   >>>>>>   
   >>>>>> I should?  Really?   
   >>>>>> Sorry, James, but you have no authority to make such statements.   
   >>>>>   
   >>>>> James is paraphrasing the C standard.   
   >>>>   
   >>>> Really?  What passage in the C standard is being paraphrased?   
   >>>   
   >>> This is advice, not paraphrased text from the C standard.  [...]   
   >>   
   >> I was responding to Scotty Lurndal's statement that the C   
   >> standard was being paraphrased (by someone, it didn't matter to   
   >> me who).  I don't care about whether his statement is true;  my   
   >> interest is only in what part of the C standard he thinks is   
   >> being paraphrased.  He is in a position to answer that question,   
   >> and more to the point he is the only person who is.   
   >   
   > It's pretty clear that the standard describes the printf   
   > function and the methods used to match the format characters   
   > to the data types of the arguments.   The fact that James   
   > framed that as advice doesn't change interpretation of   
   > the text of the standard, whether or not you consider   
   > that to be a paraphrase.   
   >   
   >   
   >   "The main rules for paraphrasing are to fully understand the   
   >   original text, restate its core idea in your own words and   
   >   sentence structure, use synonyms, and always cite the original   
   >   source to avoid plagiarism, even if the wording is different.   
      
   I see where the C standard says the macros in inttypes.h are   
   suitable for use with printf (and scanf).  That isn't at all   
   the same as saying people should use them.  Just because   
   something can be done doesn't mean it should be done.  James's   
   statement "you should use the corresponding macro" is not a   
   paraphrase, it's a statement of his opinion.   
      
   > And it is spelled "Scott".   
      
   Yes, that was an inadvertent typo, and I had already posted   
   a correction.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)