RE: SourceNav release ...

["Simonovsky, Pavel" <Pavel_Simonovsky@bmc.com>]

		So - you mean , that in fact SN is dead , and there is no
any development team behind it? It is very important info - I suggested this
tool to 2-3 teems in our company ... I have to warn them - that it dose no
worth a waste of time... Thanks a lot !!! It is really crucial
information!!!

___________________________________ 
Simonovsky Pavel 
Multiplatform CONTROL-MNew Dimension Software 
Software Engineer 
Voice: + 972 3 7664648 
Fax: + 972 3 6451100 
Email: Pavel_Simonovsky@bmc.com 

-----Original Message-----
From:	khamis2@t-online.de [mailto:khamis2@t-online.de]
Sent:	Saturday, January 05, 2002 1:43 AM
To:	Roman Levenstein
Cc:	sourcenav@sources.redhat.com
Subject:	Re: SourceNav release ...


Roman Levenstein wrote:

>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).
>>
I wasn't exact here, SN tcl parser doesn't support Itcl3.0!

>
>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. 
>
Yep!

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

>
>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.
>
Hmm, but who is familar with this toolbox? I'm not familar with the 
cocktail toolbox
and actually don't have the time to spend time learning this language.
It's true that the parsers implemented in lex/yacc are not perfekt, but 
lex is good enough
to write a parser in the 'free' time, since SN is not developed 
officially anymore!

I would appreciate very much, if you do a hack to let tcl parser 
understands
the itcl class definition "itcl:class".

khamis

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