From: "Gilles J. Seguin" <segg@infonet.ca>
To: Source Navigator <sourcenav@sources.redhat.com>
Subject: Parser, interested developpers
Date: Sun, 22 Oct 2000 11:22:00 -0000 [thread overview]
Message-ID: <39F3301B.7C47672C@infonet.ca> (raw)
In-Reply-To: <39F2F801.310677FA@cs.bilkent.edu.tr>
Eray Ozkural wrote:
>
> I've built sourcenav debian packages with the tcl/tk 8.3
> as I did for insight, but it seems that because of (at
> least) itcl compatibility it's going to fail in runtime.
>
> Meanwhile, I'm going to have to make huge debs with tcl/tk
> in 'em.
>
> In debian, we're using itcl/itk 3.1 so is the next version
> going to be using that?
> Another thing, I haven't found any development snapshots on the
> ftp site. Is that a temporary situation? Being able to look
> at some development snapshots would be very helpful at this
> point, because I might try to port the code myself, or help
> do it.
Development version,
- Where is the development CVS ?
Target/commitment was end October.
- My undersanding is that the target date for stable release
with the tcl/tk 8.3 upgrade is March 2001.
Why are deloppers out of this upgrade ?
Can we be of some help ? Or why can we ??
- What are the commodity/options that are in revision/enhancement.
Parsers need improvement. Parsers need new languages.
I will like to know who is having interest on parser.
- Documents/tools for parsing.
- Can we agree on one parser,
- Works that need to be done.
- Peoples who can be tester.
Gilles J. Seguin
segg@infonet.ca
next prev parent reply other threads:[~2000-10-22 11:22 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 ` Gilles J. Seguin [this message]
2000-10-23 9:55 ` Parser, interested developpers Syd Polk
2000-10-23 10:56 ` Eray Ozkural
2000-10-23 11:05 ` Syd Polk
2000-10-23 11:06 ` Syd Polk
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=39F3301B.7C47672C@infonet.ca \
--to=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).