On 14/04/2022 01:35, Paul Eggert wrote:
On 4/13/22 07:40, Max Nikulin wrote:
I do not see a way to get 23:30 EAT +0300.
Are you asking for a function F where you say, "I want to give F a
possibly-ambiguous decoded local time D, and for F to return all
timestamps that map to D"? If so, encode-time doesn't do that, because
the underlying C API (namely, mktime) doesn't do that. All mktime and
encode-time do is give you *one* timestamp that maps to D; it won't give
you any other timestamps.
I am just trying to convince you that new API still can not handle
ambiguities in response to:
Unfortunately it makes the function more convenient to
use incorrectly. This was part of the motivation for the API change.
The obsolescent calling convention has no way to deal with ambiguous
timestamps like 2022-11-06 01:30 when TZ="America/Los_Angeles".
Completely ignoring DST in old API is a bug. Possibility to omit DST and
ZONE is a feature for convenience and it is not related to
correctly/incorrectly. It has no common with allowing 6-values
SECONONDS...YEAR list.
I am aware of mktime and my opinion is that libc in such cases (dealing
with formats for humans) is hardly usable for applications more complex
than "hello world".
I do not want all ambiguous time values. I want to provide hints how
they should be resolved and get in response an additional value that
says in which way it is actually resolved.
If you're worried about possibly-ambiguous decoded local times, you
could probe (say) one day before and one day after encode-time's result
to see if the UTC offset changes, and let that guide you to find other
possible timestamps that map to the decoded time. Although this is just
a heuristic it should be good enough.
I would prefer to avoid dances with +/-1 day timestamps. I would not be
surprised when one day they will give wrong result. During computations
it is available to which interval of time current time offset is valid.
Such value may be included in result of conversion. So date-time +
"America/Los_Angeles" input should not be reduced to timezone offset in
the output. Zone internal object or identifier is important for
calculation of other date-time values based on the origin value.
I doubt whether you need to do that, though. Code that is not careful
about local time offsets doesn't care how ambiguous decoded times are
resolved. And code that does care should record UTC offsets anyway, and
you can use those offsets to disambiguate the decoded times. Something
like this, say:
(defun encode-and-format-time (time tz)
(let ((etime (encode-time (parse-time-string time))))
(format-time-string "%F %T %Z %z" etime tz)))
With this definition, (encode-and-format-time "2021-01-31 23:30:00
+0300" "Africa/Juba") yields "2021-01-31 23:30:00 EAT +0300", which is
the timestamp you want.
I want hints like "in the case of ambiguity resolve to transition time
immediately before/immediately after transition" or "provide suitable
time prior to/after to transition". I hope, they may work without
explicitly providing time zone offset to the input that anyway requires
additional calculations.
±n hours may mean ±n*3600 seconds or time with same minutes and seconds
values but hours value is changed by n even if a 30 min DST transition
happens in between.
If agenda interval start falls on skipped time span in local time then
the value immediately after transition should be used (and maybe user
should be warned by additional entry). For agenda end interval vice
versa local time immediately before transition is more suitable.
`parse-time-string' has another set of problems. It is impossible to
specify particular format like for strptime(3). Actually parsing a
string to numerical values and resolving ambiguities in numerical values
are different tasks and it may be useful to have separate functions for
them. I am unsure however concerning implementing constraints to parse
free-form dates.
`encode-time' should only accept time zone as time offset and should
not allow default or named value that may be ambiguous.
If we're talking about Org's encode-time substitute, you can of course
do what you like. But Emacs encode-time has supported ambiguous
timestamps for some time and I expect it's used by apps that don't care
how ambiguous decoded times are resolved, which means we shouldn't
remove that support without having a very good reason.
There is no reason to impose such restrictions for helpers in Org since
Org relies on resolving ambiguities with minimal efforts.
`encode-time' supports just one kind of ambiguities. Even though it is
the most common one, it is rather (partially false) impression than real
support.
The truth is that most of developers are not aware of real complexity of
dealing with time. Documentation rarely describes limitations and corner
cases that should be handled. Even when correct time handling gets more
priority it appears that available libraries are full of bugs and
require ugly workarounds.
should be possible to provide hints to `encode-time' to get
deterministic behavior in the case of time transitions
Yes, that feature is already there. The hint is the UTC offset, as
illustrated above.
No, UTC offset is another feature and implementing the hints I have
tried to describe may require implementing from scratch full stack of
time handling functions. In some cases offset should be replaced by time
zone identifier to avoid incorrect result in further calculations.
So I still do not see any point in mandatory DST and ZONE fields in new
interface of `encode-time'. I do not see an alternative to convert
SECONDS...YEAR values to timestamp assuming local time zone as well.
Anyway DST is not available in advance and sometimes DST value is not
coupled with step in local time, so its ability to resolve ambiguities
is limited.
