[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bison and automake together

From: Philip Herron
Subject: Re: Bison and automake together
Date: Sat, 6 Nov 2010 18:15:30 +0000

You can look at the problem in 2 ways, really you can say ylwrap is
too simplistic and not great which is correct but it does work for
standard-ish inputs like C parsers. But c++ and GLR doesnt work right
but you could say they dont comform to the standard way ylwrap expects
so it fails.

I do want to start to look into this problem with ylwrap and automake
support this week something i;ve been meaning to do for about a year
or so but havent had the time untill about now. I have some old
projects which had multiple lexer's and parsers and ylwrap could help
more in this regard which it doesnt there are tricks you can search
the mailing list for old posts about this though.


On 6 November 2010 17:06, Pippijn van Steenhoven <address@hidden> wrote:
> On Sat, Nov 06, 2010 at 04:37:26PM +0000, Paulo J. Matos wrote:
>> Does someone confirm that there is a bug here?
>> Bison in C++ mode with -y compatibility mode generates a file which
>> includes ylwrap _cannot_ rename the file or compilation will
>> fail. If C++ is supported there's a problem with ylwrap. If it's not
>> supported then Yacc shouldn't display the error and abort the build.
> In my opinion, ylwrap should gain knowledge about the used yacc
> implementation and pass a -o to it if the implementation supports it.
> That way, line numbers will be correct (aids debugging), header file
> inclusions will be correct (solves your problem) and it automatically
> allows for multiple yacc files to coexist in one project.
> --
> Pippijn van Steenhoven
> Version: GnuPG v1.4.9 (GNU/Linux)
> iEYEARECAAYFAkzVizIACgkQJc+zqGNdDgpmjgCgu153EM4ifKlkiVpb6EJdLJXx
> qigAn1HrC+EPynBJ96qty403O2aSudTO
> =r5cg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]