From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,60cf103f8ae4940d
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!feeder.news-service.com!news-out2.kabelfoon.nl!newsfeed.kabelfoon.nl!bandi.nntp.kabelfoon.nl!news.banetele.no!uio.no!fi.sn.net!newsfeed1.fi.sn.net!news.song.fi!not-for-mail
Date: Fri, 22 Aug 2008 16:29:51 +0300
From: Niklas Holsti <niklas.holsti@tidorum.invalid>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.7.8) Gecko/20060628 Debian/1.7.8-1sarge7.1
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Status of ayacc and aflex?
References: <48acd484$0$24596$4d3efbfe@news.sover.net>
 <Pine.WNT.4.64.0808221157110.9396@teor1>
 <9ceb2207-6a3d-407c-84dc-885bfaa07ec1@j22g2000hsf.googlegroups.com>
In-Reply-To: 
 <9ceb2207-6a3d-407c-84dc-885bfaa07ec1@j22g2000hsf.googlegroups.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <48aebeb3$0$23599$4f793bc4@news.tdc.fi>
Organization: TDC Internet Services
NNTP-Posting-Host: laku61.adsl.netsonic.fi
X-Trace: 1219411635 news.tdc.fi 23599 81.17.205.61:32920
X-Complaints-To: abuse@tdcnet.fi
Xref: g2news1.google.com comp.lang.ada:1762
Date: 2008-08-22T16:29:51+03:00
List-Id: <comp.lang.ada>

Ludovic Brenta wrote:
> Speaking of lexical analysis and recursive descent parsers, I'd like
> to know whether anyone here has tried OpenToken[1] and would like to
> comment on it.
> 
> [1] http://www.telepath.com/~dennison/Ted/OpenToken/OpenToken.html

I use its lexical-analysis functions a lot, for many different 
purposes. It works quite well enough for me. However, I can 
generally myself design the language to be analysed. I would not be 
surprised to find some awkward problems with languages that have 
been defined by others -- but that probably holds for any general 
lexical-scanner tool.

I very much like the absence of any "generator" step -- a simple 
"gnatmake" is enough to update the application after a change to 
the token structure.

I have not used the parsing functions in OpenToken; they did not 
exist when I started to use OpenToken, so I got into the habit of 
writing my parsers manually.

-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
       .      @       .