"Pavel Lepin" <p.lepin@c...> wrote in message
news:fjtbuf$hju$1@a......
>
> Jasper <notaround@d...> wrote in
> <2p-dnWHym_54YPzaRVnyvAA@p...>:

>
> Well, representing data like that in XML is not a problem in
> itself, even if you cannot define a more strict schema than
> just free-form key/value pairs. The problem is that you're
> probably not very likely to get the extreme performance you
> seem to want with a canned parser. DOM parsers,
> specifically, would be way too cumbersome for your needs.

Yes, I thought as much.

> So it's likely to boil down to either writing your own
> streaming parser, or using a streaming parser like expat or
> any random SAX parser out there for maximum performance,
> and even then you might not get what you need.

OK I'll take a look.

>> Would adapting an XML parser to do this be a possible
>> solution?
>
> Not enough data. Try it, profile it, there's no other way to
> know.
>
>> Any pointers/ideas/references/code snippets/observations
>> appreciated.
>
> You might want to look into S-expressions as well. You'll
> save on overhead, and I believe there are some quite fast
> S-expression parsers written in C and C++ out there.


Thanks, again.

.