clock scan strangeness

#1 08-27-2008, 06:42 AM

I was wondering why clock scan works as below:
% clock scan z
1219336516
% clock scan zz
unable to convert date-time string "zz"

and also
%clock scan ""
1219347325

it works like this with any letter. I saw that in 8.4 it was a bit
different always giving 1219266000.
what is the hidden cause for this behaviour?

#2 08-27-2008, 06:48 AM

On 27 Aug., 12:42, yahalom <yahal...@gmail.com> wrote:
> I was wondering why clock scan works as below:
> % clock scan z
> 1219336516
> % clock scan zz
> unable to convert date-time string "zz"
>
> and also
> %clock scan ""
> 1219347325
>
> it works like this with any letter. I saw that in 8.4 it was a bit
> different always giving 1219266000.
> what is the hidden cause for this behaviour?

To interpret the number returned by [clock scan], it's usually good to
[clock format] it again. I see here:

% clock format [clock scan z]
Wed Aug 27 14:45:56 CEST 2008
% clock format [clock scan now]
Wed Aug 27 12:46:09 CEST 2008
% clock format [clock scan ""]
Wed Aug 27 12:46:55 CEST 2008

So "z" gives me 2 hours ahead of "now", even though the specified
timezone is the same.

#3 08-27-2008, 06:57 AM

suchenwi wrote:
> On 27 Aug., 12:42, yahalom <yahal...@gmail.com> wrote:
>
>>I was wondering why clock scan works as below:
>>% clock scan z
>>1219336516

> So "z" gives me 2 hours ahead of "now", even though the specified
> timezone is the same.
Z ~= ZULU ~= GMT
That and the alphabet loot at:
http://wwp.greenwichmeantime.com/info/timezone.htm

uwe

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode