develooper Front page | perl.bootstrap | Postings from July 2000

RE: Working Group Proposal

From:
Fisher Mark
Date:
July 21, 2000 08:46
Subject:
RE: Working Group Proposal
Message ID:
B9B6874277EED211B1890008C707AF5302881BA9@indyexch3.indy.tce.com
>What if the lexer/parser was split out into a independent chunk of C
>code which could be linked into programming productivity tools?  Would
>that satisfy your req?

This would satisfy my upcoming requirements.  I see no problem with having 1
implementation of the Perl lexer/parser, if that implementation is easily
linkable into other projects. (Look at how many projects use expat (sp?) for
XML, which is much easier to parse than Perl.)  Although I'm desperately
short of Perl tuits right now, my mouth waters at the thought of all the
software engineering tools for Perl that could be written if we had a
pluggable lexer/parser.

If we do this, we should provide a Perl interface to the lexer parser, so we
can write some of this stuff in Perl.  I suspect that writing software
engineering tools for Perl in Perl would be easier, anyway.
===============================================
Mark Leighton Fisher            fisherm@tce.com
Thomson Consumer Electronics    Indianapolis IN
"Display some adaptability." -- Doug Shaftoe, _Cryptonomicon_




nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About