➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Alexander.Belopolsky
Recipients Alexander.Belopolsky, Arfrever, belopolsky, jcea, khenriksson, larry, lars.gustaebel, loewis, mark.dickinson, nadeem.vawda, r.david.murray, rosslagerwall, skrah, vstinner
Date 2011-09-09.21:36:54
SpamBayes Score 1.0019472e-05
Marked as misclassified No
Message-id <CAP7h-xbpZtOrQ7sTYFPV4-sd9sFm5NfLMf=zv2=bq2WFZjiFiQ@mail.gmail.com>
In-reply-to <CAP7h-xaBOV=FZBk67h89y8_c8RUDrojtAQ78jT=NOHhNuGL_GQ@mail.gmail.com>
Content 
On Fri, Sep 9, 2011 at 5:22 PM, Alexander Belopolsky
<report@bugs.python.org> wrote:
..
> If history repeats, struct stat will grow new st_xtimesuperspec
> fields, st_xtimespec will become a macro expanding to
> st_xtimesuperspec.tv_picosec

On the second thought, this won't work.  To support higher resolution
will need to supply 3 fields in st_xtimesuperspec: tv_sec and tv_nsec
packed in st_xtimespec (say tv_timespec) and new tv_psec field.
st_xtime will now be   st_xtimesuperspec.tv_timespec.tv_sec and
st_xtimespec will be a new macro expanding to
st_xtimesuperspec.tv_timespec.  The rest of my argument still holds.
History
Date User Action Args
2011-09-09 21:36:55Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, loewis, jcea, mark.dickinson, belopolsky, lars.gustaebel, vstinner, larry, nadeem.vawda, Arfrever, r.david.murray, skrah, rosslagerwall, khenriksson
2011-09-09 21:36:55Alexander.Belopolskylinkissue11457 messages
2011-09-09 21:36:54Alexander.Belopolskycreate