you could do XML, but you might then need to parse individual fields. xml
is very structured, and the nice thing is that an xml parser will do the
tokenizing work for you.
you could also use a regex library. regular expressions allow
good specification to tokenize, search, or replace text data.
otherwise you could do a hardcoded state machine, but this gets buggy, and
tedious to write.
the other method is to look at lex and yacc... with these tools you can
build a custom parser.
lex, yacc, and regex all might have some learning overhead to try to
figure out how to specify grammars or the regex to use..
@--@---@---@----@-----@------@------@-----@----@---@---@--@
Kevin Meinert __ _ __
http://www.vrac.iastate.edu/~kevn \ || \| \ / `
Virtual Reality Applications Center \ ||.-'|--\\
Howe Hall, Iowa State University, Ames Iowa \|| \| \`__,
-----------------------------------------------------------
On Tue, 26 Mar 2002, Josh Brown wrote:
> What is a good way to parce data.
>
> I'm working on storing data for multiple levels in load runner and I was
> wondering what a good way to store that information and then to parce it
> when reading it? Basically I want to know if XML is a good way to go, and
> to use a third party library to parce the files for me, or if I should
> store the data with my own rules and read it however I want to? anybody
> have ideas on this?
>
> Thanks
> Josh
>
>
> _______________________________________________
> ISUGameDev-devel mailing list
> ISU...@li...
> https://lists.sourceforge.net/lists/listinfo/isugamedev-devel
>
|
