[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: My plans for Bison: reentrant and pure
From: |
Eric S. Raymond |
Subject: |
Re: My plans for Bison: reentrant and pure |
Date: |
Wed, 13 Feb 2019 23:42:31 -0500 |
User-agent: |
Mutt/1.9.4 (2018-02-28) |
Akim Demaille <address@hidden>:
> Well, that's a feature you would like, not exactly a bug.
OK, let me back up a step.
The actual problem I have, I guess, is that I want to declare the scanner
function in my re-entrant parser in a type-safe way, not using void *.
Any day I have to use void * and casting is not a good day - it seems
like a bug that the API forces me to that.
YY_DECL is only a means to that end. Can we come uo with another way to
be type-safe that meets your concerns?
> >> I've written many reentrant parsers with Bison and Flex without the
> >> bison-bridge, I don't think it is needed.
> >
> > I have not found documentation of how to write a reentrant parser without
> > the bridge. Does any exist?
>
> I don't know, but I could improve examples/c/lexcalc to show that.
I think that would be very useful, and not just for me.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
- Re: My plans for Bison: history, (continued)
- Re: My plans for Bison: history, Akim Demaille, 2019/02/15
- Re: My plans for Bison: history, Eric S. Raymond, 2019/02/15
- Re: My plans for Bison: history, Akim Demaille, 2019/02/17
- Re: My plans for Bison: history, Akim Demaille, 2019/02/17
- Re: My plans for Bison: history, Akim Demaille, 2019/02/21
- Re: My plans for Bison: history, Eric S. Raymond, 2019/02/17
Re: My plans for Bison: reentrant and pure, Akim Demaille, 2019/02/13