From: Mo DeJong <supermo@bayarea.net>
To: sourcenav <sourcenav@sources.redhat.com>
Subject: Re: Upgrading TCL?
Date: Wed, 10 Apr 2002 11:34:00 -0000 [thread overview]
Message-ID: <20020410033923.3b568a8a.supermo@bayarea.net> (raw)
In-Reply-To: <26F9F6EAB586D411850700B0D049E6E401E11C9F@shasta.pdx.steptech.com>
On Wed, 10 Apr 2002 11:18:06 -0700
Chris Tavares <Chris@steptech.com> wrote:
> Has anyone tried to upgrade the copy of TCL shipped with Source Navigator
> 5.0.0? I've run into a couple of things that look like interpreter bugs, and
> I'm thinking that upgrading to the TCL 8.1.1 release might help things
> (considering sourcenav is still shipping with 8.1b1).
>
> Has anyone tried this? Were there any problems? Are there any changes to the
> TCL core done by sourcenav that I'd need to look out for?
Hi Chris
The Tcl 8.3 upgrade is about 97% done and can be checked out of the CVS at any time.
This is the code that will be used for a new 5.1 release (when ready). There should be
very few local changes to the SN Tcl 8.3 codebase except for the build system which
includes a lot of local mods.
cheers
Mo DeJong
prev parent reply other threads:[~2002-04-10 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 11:18 Chris Tavares
2002-04-10 11:27 ` Syd Polk
2002-04-10 11:34 ` Mo DeJong [this message]
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=20020410033923.3b568a8a.supermo@bayarea.net \
--to=supermo@bayarea.net \
--cc=sourcenav@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).