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,833 of 243,242   
   Michael =?ISO-8859-1?Q?B=E4uerle?= to Lew Pitcher   
   Re: printf and time_t   
   06 Jan 26 17:00:43   
   
   From: michael.baeuerle@gmx.net   
      
   Lew Pitcher wrote:   
   > On Tue, 06 Jan 2026 10:22:28 -0500, James Kuyper wrote:   
   > > On 2026-01-05 19:22, Lawrence D’Oliveiro wrote:   
   > > > On Mon, 5 Jan 2026 16:23:09 -0000 (UTC), Lew Pitcher wrote:   
   > > > >   
   > > > > As Andrey pointed out, time_t can resolve to a floatingpoint type,   
   > > >   
   > > > POSIX says time_t is an integer type   
   >   
   > Actually, POSIX does not say that.   
   >   
   > > > .   
   >   
   > The Debian manpages do not necessarily represent current POSIX standards.   
   >   
   > The current online POSIX standards pages say that, among others, time_t   
   > "shall be defined as arithmetic types of an appropriate length"   
   > (https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/sys_types.h.html)   
      
   Looks like you looked at an old version. Currently there is:   
   |   
   | [CX] time_t shall be an integer type with a width (see ) of at   
   least 64 bits.   
   | [...]   
   | Austin Group Defect 1462 is applied, changing time_t to have a width of at   
   least 64 bits.   
      
   It refers to this issue:   
      
      
   --- 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