Re: Is it always possible to make a non-reentrant parser reentrant?
Peng Yu <[email protected]>
| Newsgroups | gmane.comp.parsers.bison.general |
|---|---|
| Message-ID | <CABrM6wmD2xMvJyDdnfJt2ERTdTr22=J9wrrPC62kW7Dw_kK1mQ@mail.gmail.com> |
> We should probably offer an example of a pull parser in examples/c. > Have a look at the documentation to have an idea of what I mean. OK. I will take a look at it. Bash uses one parser to deal with both interactive run and non-interactive run and uses a global variable to test whether the run is interactive in many places in the code. This makes the non-interactive run inefficient. For this reason, I'd like to make two parsers --- one to deal with bash code interactively and another one to compile it (either JIT or compile it into binary) and run. Do you think this is a good strategy? How to deal with the code that is in common between the two? What is the standard practice to handle both interactive parser and non-interactive parser? Thanks. -- Regards, Peng _______________________________________________ [email protected] https://lists.gnu.org/mailman/listinfo/help-bison