[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <afd8d9b8-f6e2-4a6e-ad42-5a38e5dd75c9@cs.ucla.edu>
Date: Sun, 11 Aug 2019 17:31:48 -0700
From: Paul Eggert <eggert@...ucla.edu>
To: Rich Felker <dalias@...c.org>
Cc: libc-alpha@...rceware.org, musl@...ts.openwall.com
Subject: Re: Re: time64 abi choices for glibc and musl
Rich Felker wrote:
> this is a best-effort
> thing anyway, and can't inherently be expected to work, but the choice
> that makes things easy on the libc implementation side is *also* the
> choice that makes this work best.
It doesn't entirely simplify libc, as it enlarges struct stat and (more
importantly) makes struct stat tricky. This is a judgment call, but I would say
we're better off in the long run with a simpler struct stat that ordinary
programmers will understand easily, even if this complicates nftw implementation
during the transition.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
