Re: Problem with new version of bison's code

Sorry, I omitted the link to the new entry in the Kannel bug-tracker: https://redmine.kannel.org/issues/699#note-5 2018-08-18 11:07 GMT-05:00 Rici Lake : > This is really a problem in kannel, not in bison. Kannel's bison source > file uses a feature which has been deprecated since 2003. Support

Re: Problem with new version of bison's code

This is really a problem in kannel, not in bison. Kannel's bison source file uses a feature which has been deprecated since 2003. Support for this feature was removed with the bison 3.0 release. There's a bug in the kannel bug tracker dating from 2014, which includes a description of the problem

RE: Enhancement request: enabling Variant in C parsers

Hi Akim, > > My main concern is memory management. With Variant the destructors are > called automatically, but in C parsers I currently have to use %union with > pointers and explicit "delete". This is not exception-safe and results in ugly > code littered with "delete" statements. (Using

Re: position.hh compile error C4146 (VisualStudio 2017)

Works for me. (Not that I tried it or anything :-) I don't have Visual Studio anywhere.) 2018-08-18 10:33 GMT-05:00 Akim Demaille : > > > Le 18 août 2018 à 17:10, Rici Lake a écrit : > > > >> I don’t remember why I wrote it this way, but today I don’t care much > >> about INT_MIN here. I think

Re: Enhancement request: enabling Variant in C parsers

> Le 18 août 2018 à 17:32, Victor Khomenko a > écrit : > > Hi Akim, Hey! >> I don’t understand what you mean here, by monolithic. The parser needs a >> single type to store all the possible types, so, yes, it is monolithic. > > Well, I meant that bison looks inside the union and knows

Re: position.hh compile error C4146 (VisualStudio 2017)

On Sat, Aug 18, 2018, 10:03 Akim Demaille wrote: > Hi Rici! > > > Le 18 août 2018 à 16:45, Rici Lake a écrit : > > > > Hi, Akim > > > > I'd try > > > > return 0 < rhs || 0 - (static_cast(rhs)) < lhs > > Good idea! > > > Or the redundant but harmless > > > > return 0 < rhs ||

Re: position.hh compile error C4146 (VisualStudio 2017)

Hi Rici! > Le 18 août 2018 à 16:45, Rici Lake a écrit : > > Hi, Akim > > I'd try > > return 0 < rhs || 0 - (static_cast(rhs)) < lhs Good idea! > Or the redundant but harmless > > return 0 < rhs || static_cast(-(static_cast int>(rhs))) < lhs > > C4146 is a warning, not an error.

Re: position.hh compile error C4146 (VisualStudio 2017)

I tried it and confirmed that it works normally. Thanks, 2018-08-18 23:45 GMT+09:00 Akim Demaille : > Please keep bug-bison@gnu.org. > >> Le 18 août 2018 à 15:53, 長田偉伸 a écrit : >> >> it is still broken. >> >>> Can I install this fix? >> >>> Would you also consider reporting this bug to MS? >>

Re: position.hh compile error C4146 (VisualStudio 2017)

Hi, Akim I'd try return 0 < rhs || 0 - (static_cast(rhs)) < lhs Or the redundant but harmless return 0 < rhs || static_cast(-(static_cast(rhs))) < lhs C4146 is a warning, not an error. It's telling you that if u is unsigned, -u is still unsigned. The intent is help people avoid doing

Re: position.hh compile error C4146 (VisualStudio 2017)

Please keep bug-bison@gnu.org. > Le 18 août 2018 à 15:53, 長田偉伸 a écrit : > > it is still broken. > >> Can I install this fix? > >> Would you also consider reporting this bug to MS? > > Sorry, I can not do anything. > > Because I can understand English only a little. > (I am Japanese)

Re: position.hh compile error C4146 (VisualStudio 2017)

> Sorry, it is not clear to me: it still works, or it is still broken? it is still broken. > Can I install this fix? > Would you also consider reporting this bug to MS? Sorry, I can not do anything. Because I can understand English only a little. (I am Japanese) 2018-08-18 22:40 GMT+09:00

Re: YYEOF shouldn't be defined with bison -y

On Sat, 18 Aug 2018 06:39:36 +0200, Akim Demaille wrote: > > Hi! > > I’m coming long after the discussion, sorry. > > > Le 5 déc. 2017 à 02:32, Dimitrios Apostolou a écrit : > > > > On Mon, 04 Dec 2017 21:24:40 +0100, > > Kaz Kylheku wrote: > >> > >> On 03.12.2017 18:34, Dimitrios Apostolou

Re: position.hh compile error C4146 (VisualStudio 2017)

Hi! > Le 18 août 2018 à 07:36, 長田偉伸 a écrit : > > [Description] > >I used flex to generate the source code. >After that, when I compiled using VisualStudio 2017, an error of > C4146 occurred. > >I modified the file containing the error as follows. > ># (original)

Re: documentation: GFDL

Hi! > Le 9 oct. 2016 à 11:10, dine <2500418...@qq.com> a écrit : > > Hi-- > the documentation of GNU Bison includes a copy of the GFDL, however its title > (i.e. the name of the license) is missing. Thanks! I installed this in master (for Bison 3.1). The first part of the patch is just

position.hh compile error C4146 (VisualStudio 2017)

[Description] I used flex to generate the source code. After that, when I compiled using VisualStudio 2017, an error of C4146 occurred. I modified the file containing the error as follows. # (original) position.hh:111 return (0 < rhs || -static_cast(rhs) < lhs

Re: Reported issue is getting old

> Le 5 mars 2016 à 18:50, Balaco Baco a écrit : > > It has been more than a year since an issue has been reported, and no > reply or sign that it is known was shown. The issue is: > > 'make check' does not work for fresh 3.0 and 3.0.4 > http://savannah.gnu.org/support/?108816 > > Please

Re: [3.0.4] %printer/%destructor: simple backslashes in paths of #line statements not escaped

> Le 18 août 2018 à 10:06, Akim Demaille a écrit : > > commit adf0425d11fcb60a8171b1c004f1c013789d3a96 > Author: Akim Demaille > Date: Sat Aug 18 09:59:48 2018 +0200 > >escape properly the file names in #line for printer/destructor > >Reported by Jannick. >

Re: [3.0.4] %printer/%destructor: simple backslashes in paths of #line statements not escaped

Hi! > Le 4 mai 2017 à 22:55, Jannick a écrit : > > Thanks, J. This is the shortest (yet precise!) bug report I have ever seen! Thanks for the report. I am installing this in Bison master. It should be part of Bison 3.1.0. Cheers! commit adf0425d11fcb60a8171b1c004f1c013789d3a96 Author: