Sujet : Re: Which newsgroup for json parsing?
De : malcolm.arthur.mclean (at) *nospam* gmail.com (Malcolm McLean)
Groupes : comp.lang.cDate : 23. May 2024, 20:57:45
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <v2o73r$1tidl$1@dont-email.me>
References : 1 2 3 4
User-Agent : Mozilla Thunderbird
On 23/05/2024 18:14, Scott Lurndal wrote:
Lawrence D'Oliveiro <ldo@nz.invalid> writes:
On Thu, 16 May 2024 19:27:00 +0300, Mikko wrote:
>
Sometimes it is easier to make a parser than to use an existing one.
In this case I might try LEX.
>
Fun fact: hand-coded lexical analyzers tend to be faster than table-driven
ones like lex.
You have a warped sense of fun.
Tend to be? Any cites?
And how often does the (I suspect very marginal) performance benefits
of a hand-coded lexical analyzer surpass the development/testing cost of using
a well-tested lexical analyzer generated by lex or flex, both of which
are rather efficient?
>
I"m currently adding xpath suppport to my XML document model.
The code is here
https://github.com/MalcolmMcLean/babyxrc/blob/topic/dataimport/src/xpath.c(Baby X resource compilier, branch topic/dataimport, file xpath.c.)
It has a hand-coded lexical analyser. Now could the code be made better by moving to lex / flex?
I'm working on the code so it is currently in flux. But github stores a list of changes.
-- Check out Basic Algorithms and my other books:https://www.lulu.com/spotlight/bgy1mm