On 24 Dec 2010, at 12:54, Akim Demaille wrote:
... I would rather work on finishing glr.cc.
I may have an application for this, the functional language parser in
the folder in the link below, for the binding of the binding arrow.
Also, perhaps you missed that I asked for the state of the C
Le 24 déc. 2010 à 05:55, Joel E. Denny a écrit :
> Hi,
Hi Joel! Great to see you around.
>> No, indeed it should not. This is fixed in the current sources, which
>> have not been released yet, sorry.
>
> Would it be feasible to cherry-pick these fixes to branch-2.5? I haven't
> looked to
Hi,
On Thu, 23 Dec 2010, Akim Demaille wrote:
> Le 23 déc. 2010 à 19:31, Evan Lavelle a écrit :
>
> > I was surprised to see this in my grammars, though, since I don't use
> > %locations. Should the position/location code be generated if it's not
> > required?
>
> No, indeed it should not. T
Le 23 déc. 2010 à 19:31, Evan Lavelle a écrit :
> I was surprised to see this in my grammars, though, since I don't use
> %locations. Should the position/location code be generated if it's not
> required?
No, indeed it should not. This is fixed in the current sources, which have not
been rel
On 17 Dec 2010, at 17:08, Gergely Feldhoffer wrote:
Thank you, we upgraded bison from latest debian 2.4.1 to 2.4.3, and it
works just fine.
I just had this problem on the default Ubuntu 10.10 installation (gcc
4.4.5, bison 2.4.1). Anyone who wants to stay on 2.4.1 needs to edit the
location.
[CC the list so others get to know the state of the matter.]
You are welcome.
On 17 Dec 2010, at 17:08, Gergely Feldhoffer wrote:
Thank you, we upgraded bison from latest debian 2.4.1 to 2.4.3, and it
works just fine.
Gergely Feldhoffer
On Fri, December 10, 2010 11:24, Hans Aberg wrote:
On
I havent checked the absolute latest gcc svn for about 2 months but
yeah those are the new gcc 4.6 warnings this looks like a c++ parser
my normal c parsers havent generated any such warnings but i would
like to check also when i get a chance.
--Phil
On 10 December 2010 10:24, Hans Aberg wrote:
On 8 Dec 2010, at 15:26, Gergely Feldhoffer wrote:
... The recent version of GCC produce warnings like
position.hh: In function ‘bool example::operator==(const
example::position&, const example::position&)’:
position.hh:136:69: warning: suggest parentheses around ‘&&’ within
‘||’
[-Wparenthe
Hello,
I'm Gergely Feldhoffer, and I'm working with bison to parse some simple
languages. The recent version of GCC produce warnings like
position.hh: In function ‘bool example::operator==(const
example::position&, const example::position&)’:
position.hh:136:69: warning: suggest parentheses aroun
