Re: Defect in XBD <sys/stat.h>

[Larry Dwyer <yyyyyyyyyyy@xxxxxx>]

Hi Ulrich,

Since we can't mandate that implementations change their stat structure to 
return (or overlay) the time values with a timespec structure, why would we 
pollute this namespace?

Sure, this would allow implementations to overlay the m_time (et al) 
elements with a timespec, but no portable application can use the timespec 
overlay of m_time.  So, why pollute this namespace?

It is possible/easy for an implementation to include the overlay without 
polluting the "standard" namespace.  Why is such a solution not adequate?

                Cheers,
                Larry

At 12:10 PM 6/26/2003, yyyyyyy@xxxxxxxxxx wrote:
>         Defect report from : Ulrich Drepper , Red Hat, Inc.
>
> (Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)
>
> @ page 358 line 12708 section <sys/stat.h> comment {ud-stat-timespec}
>
> Problem:
>
> Edition of Specification (Year): 2003
>
> Defect code :  2. Omission
>
> Many systems today report acc/modification/status times in the stat 
> information with more than second resolution.  One frequently used method 
> is to report fractions of a second in nanoseconds.  I.e., the time 
> information is effectively similar to struct timespec.  In fact, some 
> systems (Linux, Solaris) could actually use struct timespec.  This would 
> probably be the preferred method.
>
> But struct timespec cannot be used in <sys/stat.h> since timespec violates 
> the namespace rules for this header.
>
> Action:
>
> Add before "Times shall be given..." on line 12708:
>
> The timespec structure may be defined as described in <sys/types.h>.