From: Keith Seitz <keiths@redhat.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: latest tcl/tk and Insight
Date: Wed, 22 Jan 2003 19:13:00 -0000 [thread overview]
Message-ID: <1043262969.1469.15.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <1043262365.1075.33.camel@Dragon>
On Wed, 2003-01-22 at 11:06, Martin M. Hunt wrote:
> Yesterday I imported tcl/tk8.4.1, itcl3.2.1, and iwidgets 4.01 into
> CVS.
Woohoo! Where's my bubbly?
> IMPROVEMENTS
> - Stable. No more crashes on cygwin.
YEAH!!!
> - Fast! You should immediately notice a dramatic improvement on
> Windows. I wrote some tests to time parts of the Insight test suite.
> For Windows, I measured it to be 2.5 - 5 times faster. For Linux, 20 -
> 30% faster.
Big YEAH!!
Ooh... I am even tempted now to squeak some extra time out of my
schedule to work on insight... Probably see about building insight with
NET releases of tcl/tk/itcl/iwidgets.. Wouldn't that be cool? :-)
Martin: great job!
Keith
next prev parent reply other threads:[~2003-01-22 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 19:03 Martin M. Hunt
2003-01-22 19:13 ` Keith Seitz [this message]
2003-01-22 20:09 ` Fernando Nasser
2003-01-23 1:06 ` 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=1043262969.1469.15.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=hunt@redhat.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).