Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c Subject: Re: printf and time_t Date: Tue, 03 Feb 2026 05:38:33 -0800 Organization: A noiseless patient Spider Lines: 38 Message-ID: <86qzr2hrqe.fsf@linuxsc.com> References: <10jfol6$2u6r8$1@news.xmission.com> <20260105105138.00005f0a@yahoo.com> <10jgbp7$2vdjt$1@news.xmission.com> <10jgdu9$2t8dh$1@nntp.eternal-september.org> <10jhkso$3c9r2$3@nntp.eternal-september.org> <20260106112938.00004446@yahoo.com> <10jj9st$3jbe4$2@dont-email.me> <20260106200522.000015ea@yahoo.com> <86jyxtpo6j.fsf@linuxsc.com> <10jm7f1$r6nl$2@dont-email.me> <864iowng6d.fsf@linuxsc.com> <_OS7R.1473208$79B9.233810@fx14.iad> <86v7hbn7cc.fsf@linuxsc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Date: Tue, 03 Feb 2026 13:38:34 +0000 (UTC) Injection-Info: dont-email.me; posting-host="72e789f1a61a439ff5daaffc25398413"; logging-data="1520319"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/o7VFTLjmphfKIcuDXDZudX3inA4+rfWQ=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:iqvSGaJYQrGyFyP/Mw5GNRimkKA= sha1:ovH72suRFNYrOt+6SaLoItFAqIQ= Xref: csiph.com comp.lang.c:396573 scott@slp53.sl.home (Scott Lurndal) writes: > Tim Rentsch writes: > >> scott@slp53.sl.home (Scott Lurndal) writes: >> >>> Tim Rentsch writes: > >>>> >>>> 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. > > Why on earth would the put them there if they didn't expect > them to be used? Expecting they will be used in some cases is different than saying they should be used in all cases.