Re: expect and tclsh give different output from "clock scan"

[Brad Gutt <bgutt3@yahoo.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1694 bytes --]

Thanks Keith.  Wow! The Expect binary and the Tcl
binary that I'm using on my PC are both coming from
the same version of Cygwin, and therefore the response
of ::tcl_platform(platform) being different is even a
more serious flaw than the issue with "clock scan"!  I
expect (pardon the pun) that Expect should be using
the exact same source code as Tcl, in fact, I would
have expected Expect to just use Tcl as a
library/framework and just add Expect-specific Tcl C
commands and procs to supply additional functionality,
just like normal Tcl based applications.  Is it that
Expect has an old copy of Tcl source in its tree? If
so, do you or anyone know why that is? Or, better yet,
is there some Expect-specific mailing list in which I
can investigate this problem further, so as to not
bother the insight group with this?

Thanks!
Brett

--- Keith Seitz <keiths@redhat.com> wrote:

> 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
> 
> 



		
__________________________________ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com