Hi, judging these docs and multiple changelog entries mentioning
`%define api.pure` as a replacement for `%pure-parser`, and the
latter being turned to wrapper on the former at some point, etc.;
I would expect that tests/input.at recommend, for `%pure_parser`,
`%define api.pure` optionally `%defin
Hi Askar,
> Le 9 déc. 2018 à 22:12, Askar Safin a écrit :
>
> Hi, Akim. Thanks a lot for your last two patches to /examples/.
Thanks for saying!
> Just a little note: your "!!", say, here: "if (!!getenv ("YYDEBUG"))" is very
> ugly. It is difficult to understand, what is going on.
Well, it's
>Please report this to them! The Makefiles are to be installed together with
>the READMEs. Here is what I have currently when I run make install:
I reported. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916084
==
Askar Safin
http://vk.com/safinaskar
Hi, Akim. Thanks a lot for your last two patches to /examples/.
Just a little note: your "!!", say, here: "if (!!getenv ("YYDEBUG"))" is very
ugly. It is difficult to understand, what is going on. Please, remove "!!" in
whole source tree.
==
Askar Safin
http://vk.com/safinaskar
> Le 9 déc. 2018 à 17:06, Askar Safin a écrit :
>
> Hi, Akim.
>
>> So I still believe the documentation, with rpcalc and mfcalc are the simple
>> examples you are asking for, and then the flex example (in examples/c, not
>> in the documentation) should be good starting points, with location
Hi, Akim.
>So I still believe the documentation, with rpcalc and mfcalc are the simple
>examples you are asking for, and then the flex example (in examples/c, not in
>the documentation) should be good starting points, with locations.
What examples/c you are talking about? I don't see "c" directo
> Le 9 déc. 2018 à 06:53, Akim Demaille a écrit :
>
>> I still think that the manual should give at least one C+Flex+Bison example
>> without locations and at least one "C++"+Flex+Bison example without
>> locations.
>
> I will not agree for two, but if you keep on insisting, then I guess th
> Le 9 déc. 2018 à 06:53, Akim Demaille a écrit :
>
>> * I give exact command lines to run my example, you don't
>
> It's an ongoing effort. If you look the history of the examples you'll see
> that they are getting Makefiles and READMEs. In particular calc++ has its
> Makefile, so your c
> Le 8 déc. 2018 à 17:06, Askar Safin a écrit :
>
> Hi, Akim.
Hi Askar!
>> This is the Bison manual, and we don't try to compete with the "flex &
>> bison" book.
> I tried to websearch this book and found it in Google Books. Google Books
> showed me preview and suggested to buy full copy.
> On 8 Dec 2018, at 07:19, Akim Demaille wrote:
>
> Hi!
>
>> Le 7 déc. 2018 à 20:30, Uxio Prego a écrit :
>>
>> I don't know of this division of parsers in pure and impure.
>>
>> Are pure approaches like GLR while LALR(k) are impure?
>
> No, it's unrelated to the parsing technology, it's
Hi, Akim.
>This is the Bison manual, and we don't try to compete with the "flex & bison"
>book.
I tried to websearch this book and found it in Google Books. Google Books
showed me preview and suggested to buy full copy. Also I found some free online
full copy, but I wonder whether it is legal.
Hi!
> Le 7 déc. 2018 à 20:30, Uxio Prego a écrit :
>
> I don't know of this division of parsers in pure and impure.
>
> Are pure approaches like GLR while LALR(k) are impure?
No, it's unrelated to the parsing technology, it's only a question
of API: whether you exchange information with the sc
> Le 6 déc. 2018 à 23:07, Askar Safin a écrit :
>
> Hi, Akim.
Hi Askar!
>> I did look at it - this example scared me off c++ parsers :-(
> I completely agree.
> I will talk about Bison 3.2.2 manual.
> If the user looks in manual and tries to find some C++ example, then he finds
> either too
Hi, Akim.
> I did look at it - this example scared me off c++ parsers :-(
I completely agree.
I will talk about Bison 3.2.2 manual.
If the user looks in manual and tries to find some C++ example, then he finds
either too simple example ("10.1.1 A Simple C++ Example", which doesn't use
Flex), eit
14 matches
Mail list logo
