From: Keith Seitz <keiths@redhat.com>
To: Brad Gutt <bgutt3@yahoo.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: expect and tclsh give different output from "clock scan"
Date: Wed, 05 Jan 2005 23:14:00 -0000 [thread overview]
Message-ID: <1104966871.2743.365.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <20041222172002.76779.qmail@web53610.mail.yahoo.com>
On Wed, 2004-12-22 at 09:20, Brad Gutt wrote:
> So, why is the output of clock scan different between
> expect and tclsh? Isn't expect using the same code as
> tclsh is using?
No, as a matter of fact, they are not using the same code. Expect on
cygwin is a "unix" application, i.e., it uses cygwin's posix layer to
call time() (from tclUnixTime.c):
expect1.1> set ::tcl_platform(platform)
unix
tclsh84> set ::tcl_platform(platform)
windows
On windows, it uses some goofy windowsy thing in tclWinTime.c to get the
time.
My guess is that cygwin/unix code and the windows code use different
epochs.
Keith
next prev parent reply other threads:[~2005-01-05 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 17:20 Brad Gutt
2005-01-05 23:14 ` Keith Seitz [this message]
2005-01-09 21:52 ` Brad Gutt
2005-01-10 1:20 ` Christopher Faylor
2005-02-20 7:29 ` Brad Gutt
2005-02-21 16:16 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1104966871.2743.365.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=bgutt3@yahoo.com \
--cc=insight@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).