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 242,782 of 243,242   
   David Brown to Andrey Tarasevich   
   Re: printf and time_t   
   05 Jan 26 11:32:18   
   
   From: david.brown@hesbynett.no   
      
   On 05/01/2026 09:17, Andrey Tarasevich wrote:   
   > On Sun 1/4/2026 11:19 PM, Kenny McCormack wrote:   
   >> The question is: How can you reliably printf() a time_t value?   
   >> What conversion spec should you use?   
   >   
   > You can't. As far as the language is concerned, `time_t` is intended to   
   > be an opaque type. It has to be a real type, so it is either an integer   
   > of a plain floating-point type. But other than that nothing is known   
   > about it. There's really no point in printing it.   
   >   
   > If you still want to, you can do it in some implementation-specific way.   
   > Which still immediately means that you can't do it "reliably", if I   
   > understand what you mean correctly.   
   >   
      
   Does being a "real type" imply that "time_t" is always an alias for a   
   standard integer type or standard floating point type?  If so, then a   
   _Generic macro might be a solution here.  If it could be an extended   
   integer type (or a _BitInt type in C23 :-) ), or some other scalar type,   
   then a _Generic macro will not cover all hypothetically possible cases.   
   But it might still cover all practical cases of interest to the OP.   
      
   --- 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