Many thanks Martin!
I was completely overlooking the behaviour for a length 1 vector with
00:00:00. More coffee needed for me I think.
Best
Tim
On 15/08/2023 08:58, Martin Maechler wrote:
Tim Taylor
on Mon, 14 Aug 2023 12:26:51 +0100 writes:
> Martin,
> Thank you. Everythin
> Tim Taylor
> on Mon, 14 Aug 2023 12:26:51 +0100 writes:
> Martin,
> Thank you. Everything you have written is helpful and I admit I am likely
guilty of using as.character() instead of format() in the past().
> Ignoring the above though, one thing I’m still unclear on i
Martin,
Thank you. Everything you have written is helpful and I admit I am likely
guilty of using as.character() instead of format() in the past().
Ignoring the above though, one thing I’m still unclear on is the special
handling of zero (or rather non-zero time) seconds in the method. Is the
> Andy Teucher
> on Fri, 11 Aug 2023 16:07:36 -0700 writes:
> I understand that `as.character.POSIXt()` had an overhaul in R 4.3
(https://github.com/wch/r-source/commit/f6fd993f8a2f799a56dbecbd8238f155191fc31b),
and I have come across a new behaviour and I wonder if it is uninte
I understand that `as.character.POSIXt()` had an overhaul in R 4.3
(https://github.com/wch/r-source/commit/f6fd993f8a2f799a56dbecbd8238f155191fc31b),
and I have come across a new behaviour and I wonder if it is unintended?
When calling `as.character.POSIXt()` on a vector that contains elements w
