On Sun, Sep 6, 2020 at 11:59 AM <xxxxxx@ancell-ent.com> wrote:

With the change from SRFI 174 to SRFI 19, set-file-times takes a couple of the latter's time objects, which are created with its make-time. Which requires a time-type as its first argument; we're currently using time-monotonic and time-utc in SRFI 170 for the posix-time and monotonic-time procedures that get the current time.

We should probably either specify that the time-type is ignored by set-file-times, or perhaps specify "it is an error" if it isn't time-utc.

There is an explicit spec in the johnwcowan repo; I just corrected it to say "it is an error if not" rather than "must".

I'm also creating time-utc time objects for file-info's (stat's) file-info:a/m/ctime fields, perhaps that should also be specified instead of assumed.

That is also explicitly specified. You'll need to pull again.

John Cowan http://vrici.lojban.org/~cowan xxxxxx@ccil.org
Newbies always ask:
"Elements or attributes?
Which will serve me best?"
Those who know roar like lions;
Wise hackers smile like tigers. --a tanka, or extended haiku