The D back-end for deterministic parsers contributed by Adela Vais is now available with the release of Bison 3.8.1 !
See https://savannah.gnu.org/forum/forum.php?forum_id=10047 for details.
Thread overview | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
September 15, 2021 Bison 3.8.1 released with D backend | ||||
---|---|---|---|---|
| ||||
The D back-end for deterministic parsers contributed by Adela Vais is now available with the release of Bison 3.8.1 ! See https://savannah.gnu.org/forum/forum.php?forum_id=10047 for details. |
September 15, 2021 Re: Bison 3.8.1 released with D backend | ||||
---|---|---|---|---|
| ||||
Posted in reply to Carl Sturtivant | Quote: *** A skeleton for the D programming language The "lalr1.d" skeleton is now officially part of Bison. It was originally contributed by Oliver Mangold, based on Paolo Bonzini's It now supports all the bells and whistles of the other deterministic Two examples demonstrate the D parsers: a basic one (examples/d/simple), |
September 15, 2021 Re: Bison 3.8.1 released with D backend | ||||
---|---|---|---|---|
| ||||
Posted in reply to Carl Sturtivant | On Wednesday, 15 September 2021 at 13:24:25 UTC, Carl Sturtivant wrote: >The D back-end for deterministic parsers contributed by Adela Vais is now available with the release of Bison 3.8.1 ! See https://savannah.gnu.org/forum/forum.php?forum_id=10047 for details. I'm sorry for being ignorant, but what does it mean to have a <insert language> back-end in Bison? Does it mean that the parser program that Assuming I'm correct: What does it matter whether the parser is a I'm really sorry I'm coming off as abrasive/ungrateful. I have no intention to belittle the author or the work she has done. But I'm really curious: What changes if I'm really sorry if this appears dismissive, I just don't know how to phrase it any better. |
September 15, 2021 Re: Bison 3.8.1 released with D backend | ||||
---|---|---|---|---|
| ||||
Posted in reply to Tejas | On Wednesday, 15 September 2021 at 14:48:06 UTC, Tejas wrote: >I'm sorry for being ignorant, but what does it mean to have a <insert language> back-end in Bison? Does it mean that the parser program that Assuming I'm correct: What does it matter whether the parser is a I'm really sorry I'm coming off as abrasive/ungrateful. I have no intention to belittle the author or the work she has done. But I'm really curious: What changes if I'm really sorry if this appears dismissive, I just don't know how to phrase it any better. A question asking for its author to be educated would be more suitably posted in the Learn forum. |
September 15, 2021 Re: Bison 3.8.1 released with D backend | ||||
---|---|---|---|---|
| ||||
Posted in reply to Tejas | On Wednesday, 15 September 2021 at 14:48:06 UTC, Tejas wrote: >Assuming I'm correct: What does it matter whether the parser is a I'm really sorry I'm coming off as abrasive/ungrateful. I have no intention to belittle the author or the work she has done. But I'm really curious: What changes if Generally speaking, a parser is not a program that you'd run in isolation. When you generate a parser with Bison, it's usually because you want to incorporate that parser into some larger program, like a compiler or a language server. In general, having Bison output its parser in $LANGUAGE makes it easier to incorporate that parser into larger programs written in $LANGUAGE. So giving Bison the ability to output D makes it easier to incorporate Bison-generated parsers into D programs. |
September 16, 2021 Re: Bison 3.8.1 released with D backend | ||||
---|---|---|---|---|
| ||||
Posted in reply to Paul Backus | On Wednesday, 15 September 2021 at 17:55:19 UTC, Paul Backus wrote: >On Wednesday, 15 September 2021 at 14:48:06 UTC, Tejas wrote: >Assuming I'm correct: What does it matter whether the parser is a I'm really sorry I'm coming off as abrasive/ungrateful. I have no intention to belittle the author or the work she has done. But I'm really curious: What changes if Generally speaking, a parser is not a program that you'd run in isolation. When you generate a parser with Bison, it's usually because you want to incorporate that parser into some larger program, like a compiler or a language server. In general, having Bison output its parser in $LANGUAGE makes it easier to incorporate that parser into larger programs written in $LANGUAGE. So giving Bison the ability to output D makes it easier to incorporate Bison-generated parsers into D programs. Yep, that's what I thought of in Discord and was validated there as well that this was it :D After a while, my mind started drifting that |
September 20, 2021 Re: Bison 3.8.1 released with D backend | ||||
---|---|---|---|---|
| ||||
Posted in reply to Carl Sturtivant | On Wed, Sep 15, 2021 at 01:24:25PM +0000, Carl Sturtivant via Digitalmars-d-announce wrote: > > The D back-end for deterministic parsers contributed by Adela Vais is now available with the release of Bison 3.8.1 ! > > https://github.com/adelavais > > See https://savannah.gnu.org/forum/forum.php?forum_id=10047 for details. Great news! T -- Unix was not designed to stop people from doing stupid things, because that would also stop them from doing clever things. -- Doug Gwyn |