public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Syd Polk <spolk@redhat.com>
To: erayo@cs.bilkent.edu.tr
Cc: "Gilles J. Seguin" <segg@infonet.ca>,
	Source Navigator <sourcenav@sources.redhat.com>
Subject: Re: Parser, interested developpers
Date: Mon, 23 Oct 2000 11:06:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20001023110708.01e89600@pop.cygnus.com> (raw)
In-Reply-To: <39F47C38.E95CEFB2@cs.bilkent.edu.tr>

At 08:58 PM 10/23/00 +0300, Eray Ozkural wrote:
>Syd Polk wrote:
> >
> > Because we have to untangle the Cygnus development tree.
>
>I built insight like that and up'ped already. You can have
>a look at it when it comes through, or I can post diffs to insight
>list. I also did sourcenav the same way, but there're a lot
>of incompatibilities with itcl.
>
>Is there any chance I could get versions of tcl code that's
>been converted to itcl3.2? If that's not available I can do
>it on my own time, learning a bit of itcl/itk in the meantime.
>I'm writing this because I wouldn't like duplication of work.
>
>Thanks,

Insight         Source-Navigator

tcl 8.0.5 (sort of)     tcl 8.1b1 (sort of)
tk 8.0.5 (sort of)      tk 8.1b1 (sort of)
itcl 3.0                itcl 1.5 (sort of)

This is the crux of the problem, and why we currently need our own copies 
of everything.


Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.



  parent reply	other threads:[~2000-10-23 11:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-22  7:53 itcl compatibility problem Eray Ozkural
2000-10-22 11:22 ` Parser, interested developpers Gilles J. Seguin
2000-10-23  9:55   ` Syd Polk
2000-10-23 10:56     ` Eray Ozkural
2000-10-23 11:05       ` Syd Polk
2000-10-23 11:06       ` Syd Polk [this message]
2000-10-22 16:17 ` itcl compatibility problem Mo DeJong
2000-10-23  9:54 ` Syd Polk

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=4.2.0.58.20001023110708.01e89600@pop.cygnus.com \
    --to=spolk@redhat.com \
    --cc=erayo@cs.bilkent.edu.tr \
    --cc=segg@infonet.ca \
    --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).