This is the mail archive of the insight@sources.redhat.com mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


On Sun, Jan 09, 2005 at 01:52:13PM -0800, Brad Gutt wrote:
>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?

Keith's analysis of the situation is correct.  expect uses a unix-like
version of tcl and insight uses a windows version of tcl with hooks for
cygwin.

Using the cygwin version of tcl for expect allows expect to use select,
ptys, and other unix-isms.  Using the windows version for insight allows
insight to draw windows on the screen.

This is a fact of life.  It isn't going to change no matter what mailing
list you discuss it in.

cgf
--
Christopher Faylor			spammer? ->	aaaspam@sourceware.org
Cygwin Co-Project Leader				aaaspam@duffek.com
TimeSys, Inc.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]