From: John Cowan <xxxxxx@ccil.org>
Date: Sunday, August 11, 2019 11:04 PM

On Sun, Aug 11, 2019 at 11:10 AM Lassi Kortela <xxxxxx@lassi.io> wrote:

[...]

current-timezone, which can be picked up from the TZ environment variable, and in general deserves being part of its own SRFI.

Agree that it should go into a date and time SRFI.

-1. I want date/time to be fully portable, no dependencies on the current anything except the current TAI-UTC table, which is unavoidable. See TimeAdvancedCowan. See also my previous post for the issue with TZ.

That's a very good point. Which means we should add back a current-timezone, properly specified as an input to the new SRFI, with how you determine it also specified, read-link magic and/or groking the format ... and don't you have to grok the formats of the two types of files to digest them?

- Harold