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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.66.132.7 with SMTP id oq7mr39149074pab.7.1433295830700; Tue, 02 Jun 2015 18:43:50 -0700 (PDT) X-Received: by 10.182.28.227 with SMTP id e3mr194335obh.33.1433295830662; Tue, 02 Jun 2015 18:43:50 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!h15no1252471igd.0!news-out.google.com!n7ni51366igk.0!nntp.google.com!h15no2286942igd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 2 Jun 2015 18:43:50 -0700 (PDT) In-Reply-To: <85twupvjxo.fsf@stephe-leake.org> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=67.0.105.201; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 67.0.105.201 References: <878uc3r2y6.fsf@adaheads.sparre-andersen.dk> <85twupvjxo.fsf@stephe-leake.org> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <81ceb070-16fe-4578-a09a-eb11a2bbb664@googlegroups.com> Subject: Re: OpenToken: Parsing Ada (subset)? From: Shark8 Injection-Date: Wed, 03 Jun 2015 01:43:50 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:26145 Date: 2015-06-02T18:43:50-07:00 List-Id: On Tuesday, June 2, 2015 at 4:12:37 PM UTC-6, Stephen Leake wrote: >=20 > Obvious to me, but I've been messing with the lexer code in FastToken > recently; I switched to using regular expressions for the token > recognizers (to be closer to Aflex, which is also now supported). While > doing that, I deleted the default Get above. >=20 > Using regular expressions instead of the old OpenToken recognizers is a > big change, but wisi-generate takes care of most of the drudge work for > you (you just have to specify the actual regular expressions). Is that a good idea? >From my experience [mainly maintenance] RegEx is almost always a bad soluti= on (though I will grant that most of my encounters w/ it involved applying = it as a formatting/parsing tool for items that generally weren't amiable to= such breakdowns [street addresses, for example, are good at containing inf= o/formatting that kills a simple regex]).