Georgios Petasis <
peta...@yahoo.gr> wrote:
> Στις 17/11/2017 00:19, ο Gerald Lester έγραψε:
>> On 11/16/2017 03:30 PM,
walto...@gmail.com wrote:
>>> On Thursday, November 16, 2017 at 11:42:19 AM UTC-6, Georgios Petasis
>>> wrote:
>>>> clock format [clock scan {2004-10} -format {%Y-%m}]
>>> It returns the first hour/min/sec (midnight) when the time is dropped,
>>> so it seems like the logical thing for it to do when the day is
>>> dropped is use the first day of the month.
>> Rule #7 on the SCANNING TIMES section of the [clock] man page.
> I have given a year, so this is a perfectly and complete defined date.
> 2004 is a perfectly defined date by iso 8601.
Note the notion of "complete set" in [3]. It's not just about the year.
> So, if giving 2004 you are getting back 2017 instead of 2004, and this
> is justified by the rules, then the rules are seriously flawed.
Without such a complete set, there are just too many ambiguities to get sane
semantics. It could be feasible to define some "partial" sets that might
also be used to define a date (with defined defaults for the remaining fields),
but clock scan is already complex enough, έτσι δεν είναι;