From: khamis2@t-online.de (Khamis Abuelkomboz)
To: klmcw@yahoo.com
Cc: sourcenav@sources.redhat.com
Subject: Re: SourceNav release ...
Date: Thu, 03 Jan 2002 15:08:00 -0000 [thread overview]
Message-ID: <3C34E286.4030308@t-online.de> (raw)
In-Reply-To: <3C34DB94.E2D0667F@yahoo.com>
Except my additions and bug fixes there is at this time no other work.
Especially regarding parsers (c++ and java) nothing happens and will
happen in the next time.
Actually I'm interested to know
- how many people use SN to browse into tcl language?
- how many people use cross-reference to tcl language?
because the actual tcl parser is written in a strange licenced
interpreter "rex?" and
redhat don't have the origin source code and the license to this parser.
Also SN tcl parser doesn't support tcl/tk8.x. So if there are enough people
interested in this I would start writing a new parser (using flex) for
tcl that supports
tcltk8.x (without xref).
P.S. the tcl xref is pretty ugly and doesn't provide any interesting
information.
Khamis
klmcw yahoo wrote:
>Is there another release scheduled for SourceNav ?
>
>I love the tool, but it fails to cross-reference most of the projects I
>have to deal with.
>Thanks.
>-Kevin
>
>
>
next prev parent reply other threads:[~2002-01-03 23:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 14:30 klmcw yahoo
2002-01-03 15:08 ` Khamis Abuelkomboz [this message]
2002-01-04 2:56 Roman Levenstein
2002-01-04 15:48 ` Khamis Abuelkomboz
2002-01-06 0:26 Simonovsky, Pavel
2002-01-06 3:48 ` Mo DeJong
2002-01-06 6:36 ` Ralf Corsepius
2002-01-07 12:04 ` Khamis Abuelkomboz
2002-01-07 13:11 ` Timothy M. Shead
2002-01-18 18:13 ` Mo DeJong
2002-01-07 13:22 ` Ian Roxborough
2002-01-10 4:34 ` Eray Ozkural (exa)
2002-01-11 14:34 ` Mo DeJong
2002-01-18 14:52 ` Eray Ozkural (exa)
2002-01-18 15:33 ` Mo DeJong
2002-01-18 15:58 ` Ian Roxborough
2002-01-24 10:14 ` Eray Ozkural (exa)
2002-01-19 9:03 ` Eray Ozkural (exa)
2002-01-19 8:59 ` Khamis Abuelkomboz
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=3C34E286.4030308@t-online.de \
--to=khamis2@t-online.de \
--cc=klmcw@yahoo.com \
--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).