On Jan 20, 2011, at 3:31 PM, Iñaki Baz Castillo wrote: > 2011/1/21 Benjamin van der Veen <[email protected]>: > >> It seems to me that a common problem faced by users of Ragel is that they do >> not know in advance where (with respect to the grammar being parsed) the >> boundaries of buffers that they feed the parser are going to be. For >> example, I can easily make a Ragel grammar which will parse the following >> using only entering and leaving actions: > > I recommend you checking Mongrel HTTP parser, which is written in C > and it used to build a Ruby object containing parsed data. However the > parser is a separate file(s) you really can learn from.
Mongrel is where I got the idea from, although it seems to buffer the entirety of the request headers to work around this problem. I would like to avoid this solution if possible.
_______________________________________________ ragel-users mailing list [email protected] http://www.complang.org/mailman/listinfo/ragel-users
