Re: Question on parsing streaming input in Bison/Bison++

[Sriram Sankar]

Thanks for the response. I'm using TCP sockets and that makes sure
the packets come in sequentially. Also I'm trying to avoid the
multithreaded idea since the context switching in Linux is very slow.
I have a callback system where the requests are broken into subtasks
and get queued and and once the subtasks get handled, a callback function
is called to handle the next step.

-Sriram


Hans Aberg wrote:

> At 17:08 -0800 0-11-29, Sriram Sankar wrote:
> >    I have a question on parsing streaming input (asynchronous socket).
> >I am using Flex (C++ option) and Bison. Now I'll be moving over to
> >Bison++.
> >    I'll be getting the data stream through an asynchronous socket.
> >The current implementation gets all the data and then lex/parse it.
> >For performance improvement, I'm thinking of parsing blocks of data as
> >they come in.
>
> My guess is that you have the situation where the input to be parsed comes
> in blocks block_1, block_2, ..., and further, it may happen that the they
> arrive in in a different order from their logical order: So even though,
> for i < j, block_i logically comes before block_j, block_j may arrive
> before block_i. You then want to parse the blocks as they arrive, and then
> somehow pick together their semantics. Right?
>
> I do not know much about this type of programming, but could you not first
> identify each block, and then parse each block in a separate thread
> Flex/Bison combination (which must be pure or "re-entrant" without global
> data). Then you need to write something that picks together the semantic
> value produced by each thread.
>
>   Hans Aberg