Prev: tcl, tclreadline and expect issue
Next: Tk [photo]: when does a dithering process occur ?
From: yahalom on 28 Jul 2010 04:45
I see no difference between "clock scan now" and "clock scan today"
also today is inconsistent with other relative dates

doing:
%clock format [clock scan yesterday]

%Mon Jul 19 00:00:00 IDT 2010

%clock format [clock scan tomorrow]

Wed Jul 21 00:00:00 IDT 2010

%clock format [clock scan today]

%Tue Jul 20 14:41:13 IDT 2010

which is same as

%clock format [clock scan now]

I would expect:
%clock format [clock scan today]

%Tue Jul 20 00:00:00 IDT 2010

is this a bug?
From: Roy Terry on 28 Jul 2010 12:21
On Jul 28, 1:45 am, yahalom <yahal...(a)gmail.com> wrote:
> I see no difference between "clock scan now" and "clock scan today"
> also today is inconsistent with other relative dates
>
> doing:
> %clock format [clock scan yesterday]
>
> %Mon Jul 19 00:00:00 IDT 2010
>
> %clock format [clock scan tomorrow]
>
> Wed Jul 21 00:00:00 IDT 2010
>
> %clock format [clock scan today]
>
> %Tue Jul 20 14:41:13 IDT 2010
>
> which is same as
>
> %clock format [clock scan now]
>
> I would expect:
> %clock format [clock scan today]
>
> %Tue Jul 20 00:00:00 IDT 2010
>
> is this a bug?

I have the same question.
From: Bruce on 29 Jul 2010 15:43
yahalom wrote:
> I see no difference between "clock scan now" and "clock scan today"
> also today is inconsistent with other relative dates
>
> doing:
> %clock format [clock scan yesterday]
>
> %Mon Jul 19 00:00:00 IDT 2010
>
> %clock format [clock scan tomorrow]
>
> Wed Jul 21 00:00:00 IDT 2010
>
> %clock format [clock scan today]
>
> %Tue Jul 20 14:41:13 IDT 2010
>
> which is same as
>
> %clock format [clock scan now]
>
> I would expect:
> %clock format [clock scan today]
>
> %Tue Jul 20 00:00:00 IDT 2010
>
> is this a bug?

to quote from the clock manual page:

FREE FORM SCAN
If the clock scan command is invoked without a -format option, then it
requests a free-form scan. This form of scan is deprecated. The reason
for the deprecation is that there are too many ambiguities. (Does the
string �2000� represent a year, a time of day, or a quantity?) No set of
rules for interpreting free-form dates and times has been found to give
unsurprising results in all cases.


so - don't use deprecated features if you want consistency

use the -format option and specify a consistent time base

bruce
From: yahalom on 29 Jul 2010 23:09
On Jul 30, 12:43 am, Bruce <Bruce_do_not_...(a)example.com> wrote:
> yahalom wrote:
> > I see no difference between "clock scan now" and "clock scan today"
> > also today is inconsistent with other relative dates
>
> > doing:
> > %clock format [clock scan yesterday]
>
> > %Mon Jul 19 00:00:00 IDT 2010
>
> > %clock format [clock scan tomorrow]
>
> > Wed Jul 21 00:00:00 IDT 2010
>
> > %clock format [clock scan today]
>
> > %Tue Jul 20 14:41:13 IDT 2010
>
> > which is same as
>
> > %clock format [clock scan now]
>
> > I would expect:
> > %clock format [clock scan today]
>
> > %Tue Jul 20 00:00:00 IDT 2010
>
> > is this a bug?
>
> to quote from the clock manual page:
>
> FREE FORM SCAN
> If the clock scan command is invoked without a -format option, then it
> requests a free-form scan. This form of scan is deprecated. The reason
> for the deprecation is that there are too many ambiguities. (Does the
> string “2000” represent a year, a time of day, or a quantity?) No set of
> rules for interpreting free-form dates and times has been found to give
> unsurprising results in all cases.
>
> so - don't use deprecated features if you want consistency
>
> use the -format option and specify a consistent time base
>
> bruce

I can accept that a format is needed when using "2000" or similar
string but what format can I specify for the word "today" that will
make it more clear? and if "today" is not clear then what about
"yesterday" and "tomorrow"? for me it seems inconsistent and something
that should change even in the price of backward compatibility as you
can always change "today" to "now" to keep they way you used to do it.
From: Aric Bills on 29 Jul 2010 23:37
On Jul 29, 9:09 pm, yahalom <yahal...(a)gmail.com> wrote:
> On Jul 30, 12:43 am, Bruce <Bruce_do_not_...(a)example.com> wrote:
>
>
>
> > yahalom wrote:
> > > I see no difference between "clock scan now" and "clock scan today"
> > > also today is inconsistent with other relative dates
>
> > > doing:
> > > %clock format [clock scan yesterday]
>
> > > %Mon Jul 19 00:00:00 IDT 2010
>
> > > %clock format [clock scan tomorrow]
>
> > > Wed Jul 21 00:00:00 IDT 2010
>
> > > %clock format [clock scan today]
>
> > > %Tue Jul 20 14:41:13 IDT 2010
>
> > > which is same as
>
> > > %clock format [clock scan now]
>
> > > I would expect:
> > > %clock format [clock scan today]
>
> > > %Tue Jul 20 00:00:00 IDT 2010
>
> > > is this a bug?
>
> > to quote from the clock manual page:
>
> > FREE FORM SCAN
> > If the clock scan command is invoked without a -format option, then it
> > requests a free-form scan. This form of scan is deprecated. The reason
> > for the deprecation is that there are too many ambiguities. (Does the
> > string “2000” represent a year, a time of day, or a quantity?) No set of
> > rules for interpreting free-form dates and times has been found to give
> > unsurprising results in all cases.
>
> > so - don't use deprecated features if you want consistency
>
> > use the -format option and specify a consistent time base
>
> > bruce
>
> I can accept that a format is needed when using "2000" or similar
> string but what format can I specify for the word "today" that will
> make it more clear? and if "today" is not clear then what about
> "yesterday" and "tomorrow"? for me it seems inconsistent and something
> that should change even in the price of backward compatibility as you
> can always change "today" to "now" to keep they way you used to do it.

I agree. "today" ought to be unambiguous enough, and, like the
original poster, I would expect it to produce results analogous to
"yesterday" and "tomorrow". I think Kevin Kenny is the architect of
the [clock] command; if you can catch his attention, he's probably the
one who can give the most authoritative answer.
 |  Next  |  Last
Pages: 1 2 3 4
Prev: tcl, tclreadline and expect issue
Next: Tk [photo]: when does a dithering process occur ?