home bbs files messages ]

Just a sample of the Echomail archive

COMPLANC:

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

 Message 242,837 of 243,097 
 James Kuyper to Lew Pitcher 
 Re: printf and time_t 
 06 Jan 26 11:19:14 
 
From: jameskuyper@alumni.caltech.edu

On 2026-01-06 11:08, Lew Pitcher wrote:
> On Tue, 06 Jan 2026 17:00:43 +0100, Michael Bäuerle wrote:
>
>> Lew Pitcher wrote:
...
>>> 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/s
s_types.h.html)

I followed the link Lew provided, and found precisely the text quoted by
Michael:

>> 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.

The part where it says that time_t shall be an integer type is in a
separate section titled "Additionally", 27 lines of text after it says
"shall be defined as arithmetic types ...".

> Do you have a URL reference for this? I got my POSIX references direct from
the Open Group's
> "current standards" links. The time(2),  and  webpages
are all
> headed:
>   The Open Group Base Specifications Issue 8
>   IEEE Std 1003.1-2024
>
> Perhaps they have not yet applied the defect remediation to the online
reference.

--- 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