Guido Jäkel <g.jae...@dnb.de> writes: > Dear Pádraig, > > thank you for clarification! And for the pointer to the FAQ. With the > assumption that the time shifts all over the world will happen before > noon, this will be a "working workaround". And IMHO, this must be > called a workaround and not a "have-to-known" , because it fixes the > current implementation to yield a result that will match the suggested > semantic of input.
To give a different point of view, I'm not sure your suggested semantic here is the only reasonable interpretation. The semantic you seem to want is "same time as now only yesterday". However you ask for "1 day ago". I think it is not unreasonable to interprete "1 day ago" to mean "24 hours ago". https://en.wikipedia.org/wiki/Day If we change "1 day ago" to take into account daylight savings changes and make adjustment, I suspect we will get reports that complain that "1 day ago" sometimes mean 23 or 25 hours instead of always 24 hours. I think that would be a valid complaint too. Maybe the solution isn't to flip-flop the implementation here, but to document this concern and some method to disambiguate how to reliably get the intended semantics. For some applications, "1 day" can be defined as 86400 seconds just like SI. For some applications, "1 day" can be defined to mean 86400 seconds except when DST occured where it can be 23 or 25 hours instead. For some applications, "1 day" can probably mean something entirely different too (24 hours 40 minute Mars days anyone?). /Simon
signature.asc
Description: PGP signature
