public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Roman Levenstein <romixlev@yahoo.com>
To: sourcenav@sources.redhat.com
Subject: Re: SourceNav release ...
Date: Fri, 04 Jan 2002 02:56:00 -0000	[thread overview]
Message-ID: <20020104105639.67195.qmail@web11504.mail.yahoo.com> (raw)

Hi,

>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).

The Rex scanner generator is a part of the Cocktail
Toolbox, which is also used for other SN parsers such
as  Cobol and Java parsers. 

There is a public domain version of it, which can be
found at:
http://www.gmd.de/SCAI/lab/adaptor/cocktail.html

So, there is no problem with a licence. 

As for the origin source for the *.rex file, it's also
not a problem. REX specification is generated from
*.scan file by cg tool as far as I remember. Anyway,
there is a description of this process in the docs.

BTW, Cocktail is one of the best compiler construction
toolkits and it's really very powerful and much better
than yacc/lex. It covers the whole process of compiler
construction- from lexical and syntax analysis up to
code generation and register allocation. And, which is
also very important, the generated parsers and
scanners   are much faster than those generated by
lex/yacc.

Roman 



__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

             reply	other threads:[~2002-01-04 10:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04  2:56 Roman Levenstein [this message]
2002-01-04 15:48 ` Khamis Abuelkomboz
  -- strict thread matches above, loose matches on Subject: below --
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
2002-01-03 14:30 klmcw yahoo
2002-01-03 15:08 ` 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=20020104105639.67195.qmail@web11504.mail.yahoo.com \
    --to=romixlev@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).