Source-Changes-D archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: CVS commit: src/lib/libutil
Date: Wed, 1 May 2024 22:27:02 +0200
From: Roland Illig <roland.illig%gmx.de@localhost>
Message-ID: <754bd755-be0a-4eff-aa7b-d53fce9b4ccc%gmx.de@localhost>
| > Log Message:
| > next should increement by 1 not 2.
|
| Are you sure?
I agree, that change should be reverted.
"next" is even documented to be two ...
6 Despite what is stated above, ?next? is actually 2. The input ?next
January?, instead of producing a timestamp for January of the
following year, produces one for January 2nd, of the current year.
Use caution with ?next? it rarely does what humans expect. For
example, on a Sunday ?next sunday? means the following Sunday (7 days
hence) whereas ?next monday? means the monday that follows that (8
days hence) rather than ?tomorrow? or just ?Mon? (without the ?next?)
which is the nearest subsequent Monday.
and is actually more useful that way. It is peculiar, but that's how it
has worked ~forever.
There are limits to how sane a half hearted (but still useful) attempt
to understand English idiom can possibly work, we really don't want to
attempt to turn parsedate into an AI machine.
kre
Home |
Main Index |
Thread Index |
Old Index