From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4629 invoked by alias); 4 Jan 2002 10:56:44 -0000 Mailing-List: contact sourcenav-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sourcenav-owner@sources.redhat.com Received: (qmail 4585 invoked from network); 4 Jan 2002 10:56:39 -0000 Message-ID: <20020104105639.67195.qmail@web11504.mail.yahoo.com> Date: Fri, 04 Jan 2002 02:56:00 -0000 From: Roman Levenstein Subject: Re: SourceNav release ... To: sourcenav@sources.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-q1/txt/msg00007.txt.bz2 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