On 29 May 2007, at 11:49, Frans Englich wrote:
I'm switching a parser to be GLR in order to simplify the lexer.
It's all in
C++, the parser & tokenizer must be exceptions safe(hence, Bison
destructors
cannot be used to free values, as far as I know), and it must be
reentrant.
My current p
On Tuesday 29 May 2007 12:02, Tim Van Holder wrote:
> Frans Englich wrote:
> > Hello,
> >
> > What direction do you recommend me to take?
> >
> > I like the C skeleton because it's simple and it doesn't have
> > dependencies on the STL, which is a no go for me, unfortunately. So, I
> > simply need
Frans Englich wrote:
> Hello,
>
> What direction do you recommend me to take?
>
> I like the C skeleton because it's simple and it doesn't have dependencies on
> the STL, which is a no go for me, unfortunately. So, I simply need a
> parser(GLR, or non GLR, if necessary) that can have non-POD se
Hello,
I'm switching a parser to be GLR in order to simplify the lexer. It's all in
C++, the parser & tokenizer must be exceptions safe(hence, Bison destructors
cannot be used to free values, as far as I know), and it must be reentrant.
My current parser does not use the C++ skeleton despite b
