[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: parser validation tools

• Subject: Re: parser validation tools
• From: "Richard G. Ball" <richard_ball@xxxxxxxxx>
• Date: Thu, 11 May 2000 16:41:55 +0100 (BST)

On May 11,  4:05pm, Bollinger, John Clayton wrote:
> The common theme among all of those items seems to be that they are
> aimed at easing parsing via _record-oriented_ file handling, ala
> Fortran.  They are no special boon when using stream-oriented file
> handling, ala C, Java, and others.

Yes and no. It would help the record-oriented readers but it also would
assist the grabbing tokens from a stream. My parser is in perl and it almost
handles all the cases in Brian's ciftest5 file but I could simplify the
matching expressions and other token/data extraction code if I could make
some assumptions about the stream's structure.

Now I am not a lex programmer so I don't know how difficult it would be to
take a complete BNF descriptor for CIF and turn it into a parser with a nice
set of C/F77/perl/? bindings. Anyone?

Richard

--
Dr R.G. Ball                    |  voice: 732-594-5341
Merck Research Laboratories     |  fax: 732-594-6793 or 6100
PO Box 2000, R50-105            |  email: Richard_Ball@merck.com
Rahway, NJ  07065   USA

Reply to: [list | sender only]

• Prev by Date: RE: parser validation tools
• Next by Date: RE: parser validation tools
• Prev by thread: RE: parser validation tools
• Next by thread: RE: parser validation tools
• Index(es):
  • Date
  • Thread