Email List: Xaustin-review-lX
[All Lists]

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

To: yyyyyyyyyyyyyyy@xxxxxxxxxxxxx
Subject: Re: Defect in XBD <sys/stat.h>
From: Larry Dwyer <yyyyyyyyyyy@xxxxxx>
Date: Thu, 26 Jun 2003 15:21:01 -0700
References: <5.1.0.14.0.20030626122353.03bf9cd0@xsvr9.cup.hp.com><5.1.0.14.0.20030626122353.03bf9cd0@xsvr9.cup.hp.com>
But I asked:

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

Hey, I can suggest adding lots of extensions that are in HP-UX suitably couched with the qualifier "may", but how would that be useful to the application developer who is trying to write portable code?

I don't see the need for this extension in a portability standard.

Cheers,
Larry


At 12:33 PM 6/26/2003, Ulrich Drepper wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Larry Dwyer wrote:

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

Did you see the "may" in my proposed text?  No requirement to pollute
the namespace, but if it happens to be useful it should be allowed.

- --
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE++0qa2ijCOnn/RHQRApavAJ9Ur5rnws2lO3FPUABuqrGUM6MnKgCgzNlI
1i0Dyq9VgrkZWlL825gM/pI=
=1COb
-----END PGP SIGNATURE-----





<Prev in Thread] Current Thread [Next in Thread>