From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28075 invoked by alias); 10 Jan 2005 01:20:51 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 27957 invoked from network); 10 Jan 2005 01:20:44 -0000 Received: from unknown (HELO cgf.cx) (66.30.17.189) by sourceware.org with SMTP; 10 Jan 2005 01:20:44 -0000 Received: by cgf.cx (Postfix, from userid 201) id BA87D1B522; Sun, 9 Jan 2005 20:20:47 -0500 (EST) Date: Mon, 10 Jan 2005 01:20:00 -0000 From: Christopher Faylor To: insight@sources.redhat.com Subject: Re: expect and tclsh give different output from "clock scan" Message-ID: <20050110012047.GA27333@trixie.casa.cgf.cx> Reply-To: insight@sources.redhat.com Mail-Followup-To: insight@sources.redhat.com References: <1104966871.2743.365.camel@lindt.uglyboxes.com> <20050109215213.99039.qmail@web53603.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050109215213.99039.qmail@web53603.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-SW-Source: 2005-q1/txt/msg00005.txt.bz2 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.