>> This is not possible as Spirits recursive descent parser framework stores
>> the current parser state on the (hardware-) stack. In order to do the
>> context switch in between two parse steps you need to use some co-routine
>> library. But this is non-trivial and requires some changes to Spirit
>> itself.
>>
> Thank you.
>
> Could a feature request be made so that the Spirit Framework could be
> used to parse content sent over a network connection?
>
> Would the rest of the community find such a feature useful?
>
> Kind Regards,
> Etienne
IMHO this feature would be very usefull. I personally use Spirit to parse
HTTP headers. This works fine. But currently I have to check the end of the
HTTP header "\r\n\r\n" in a special way and after detecting the end,
the parser will called. It all boils down to parse the byte stream twice!
If Spirit could store it's internal state, it would be great. The biggest
would be, to accept boost::asio::tcp::iostream as parser input.
Cmd. Pirx
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at:
http://p.sf.net/sfu/Challenge_______________________________________________
Spirit-general mailing list
Spirit-general@...
https://lists.sourceforge.net/lists/listinfo/spirit-general
