Hi Paolo,
Below is discussed a difference bw the Java parsers and the others.
What opinion do you have about it? Do you see a means to converge?
Le 7 sept. 2009 à 09:55, Akim Demaille a écrit :
Hi,
I was tired to read
%parse-param {::parser::ParserImpl& up}
%lex-param {::pa
o send check-in mails is broken.
From a7706735d143e3d7ab255e162499584e5337ba72 Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Thu, 3 Sep 2009 14:15:13 +0200
Subject: [PATCH 1/6] %param.
Provide a means to factor lex-param and parse-param common
declarations.
* src/parse-gram.y (p
installed in master (no such code in 2.5).
* data/c++.m4 (b4_public_types_define): Add missing inline to
implementations provided in headers.
From 2966006237cce1132f8fb4eca2ac9933b431eb51 Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Tue, 8 Sep 2009 21:59:33 +0200
Subject
pt.
From ff601366544d2cb2218c80e37083a88c6102061c Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Tue, 8 Sep 2009 22:00:13 +0200
Subject: [PATCH 2/2] lalr1.cc: syntax_error as exceptions.
It is common to use sort of factories in the user actions. These
factories may check some "syntactic" constraints t
Le 10 sept. 2009 à 07:16, Joel E. Denny a écrit :
I'd like to push this patch to master and branch-2.5. I need it for
that
lookahead correction implementation I spoke about recently, but I
think
it's worthwhile on its own as well. Any objections? I haven't
looked at
porting this to the
Le 11 sept. 2009 à 23:49, Joel E. Denny a écrit :
Anyway, which one sounds better in English ?
In general, I think they both sound fine. I just think "symbolic
references" is ambiguous in the context of grammars. What do you
think,
Akim?
I also prefer "named", especially since we are p
Le 12 sept. 2009 à 11:19, Alex Rozenman a écrit :
Hi,
I pushed the attached patch to master/branch-2.5. It adds an
additional
sub-message in case of "invalid references" for clarity. I will
submit NEWS
changes as a separate commit (we need to finalize terminology).
Hi Alex,
This is nic
Le 13 sept. 2009 à 22:01, Joel E. Denny a écrit :
I'd like to push this patch to master, branch-2.5, and branch-2.4.2 so
that push parser users are informed that they can't set
YYSTACK_USE_ALLOCA=1. The only way I can see to do this is with
#error in
yacc.c. However, I don't see any other u
Le 13 sept. 2009 à 22:31, Joel E. Denny a écrit :
Hi Akim.
I'm finding bench.pl to be quite useful. :)
Good :)
I'd like to push this patch to master, branch-2.5, and maybe even
branch-2.4.2 in case it might be around a little longer. Any
objections?
* etc/bench.pl.in (generate_gramma
Le 14 sept. 2009 à 23:43, Alex Rozenman a écrit :
Hi Akim, Hi Joel, All,
I would like to install the following (attached) patch in order to
make the
error messages more readable. Please review the presented mechanism
and let
me know if there are any objections/comments.
Hi Alex,
I have constant demand for Bison 2.4.2 (from a colleague who is
sitting a few meters away from me ;), so let's move forward. I hoped
that 2.4.2 would have an updated exception clause, but it seems we'll
have to do that in 2.4.3, or maybe 2.5.
Joel and I would like to include in the NEWS fi
Le 11 sept. 2009 à 09:40, Joel E. Denny a écrit :
+# gcc warns about tautologies and fallacies involving comparisons for
+# unsigned char. However, it doesn't produce these same warnings for
+# size_t and many other types when the warnings would seem to make
just
+# as much sense. We ignor
Le 8 sept. 2009 à 01:42, Joel E. Denny a écrit :
My grammar has:
- 185 rules
- 104 terminals
- 58 nonterminals
How many S/R and R/R conflicts? I'm also interested in conflicts
that are
resolved by prec/assoc declarations.
There are no remaining conflicts. The updated log has the figure
ation_type& l)
{
return symbol_type (token::TOK_CASE, l);
}
I suppose it does have an impact of the object file, but I have not
checked.
From 2b08bcebf082a2417ef5706b5ae0664ce844f16e Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Wed, 9 Sep 2009 23:09:22 +0200
Subject: [PATCH]
/ChangeLog
@@ -1,5 +1,10 @@
2009-09-16 Akim Demaille
+ doc: comment changes.
+ * doc/bison.texinfo: Comment changes.
+
+2009-09-16 Akim Demaille
+
lalr1.cc: factor the yytranslate_ invocation in make_SYMBOLS.
* data/c++.m4, data/lalr1.cc (parser::symbol_type
Akim Demaille
+ doc: spell checking.
+ * doc/bison.texinfo: here.
+
+2009-09-16 Akim Demaille
+
doc: comment changes.
* doc/bison.texinfo: Comment changes.
diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index e253314..adfd7f4 100644
--- a/doc/bison.texinfo
| 25 +++
doc/bison.texinfo | 509 ++---
2 files changed, 428 insertions(+), 106 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index bf7c496..504b0f5 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,30 @@
2009-09-16 Akim Demaille
+
Le 17 sept. 2009 à 09:02, Alex Rozenman a écrit :
Hi Akim,
Hi Alex!
Before I'll proceed, could you please verify that I understand the
'gettext' correctly ?
It's simple if you understand that there are two phases. The first
one is static: you need special mark up so that the strings to
Le 16 sept. 2009 à 19:06, tys lefering a écrit :
On Wed, September 16, 2009 16:32, Akim Demaille wrote:
It would be nice to extend the *.output file with various metrics
about the grammar.
Agreed.
Will add this to TODO.
About this metrics feature: there is a patched bison version
with a
@@
+2009-09-17 Akim Demaille
+
+ doc: fixes.
+ * doc/bison.texinfo: here.
+ Reported by Alex Rozenman.
+
2009-09-16 Akim Demaille
doc: lalr1.cc and variants.
diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index e38bfa5..8f40afb 100644
--- a/doc/bison.texinfo
On master only.
From 5ad90d528dc5feedb0c1d8afe82719440ec17217 Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Thu, 17 Sep 2009 09:41:21 +0200
Subject: [PATCH] todo: short term
* TODO (syntax_error, variable names): New.
---
TODO | 22 ++
1 files changed, 22
Le 17 sept. 2009 à 10:59, Alex Rozenman a écrit :
Akim,
But that's too complex for them (most are not programmer), and it
might not
even suffice to always produce nice translations. That's why I
suggest that
you de-factor and truly expose the two full format-strings: get rid
of
msg[123]
Le 26 sept. 2009 à 06:24, Joel E. Denny a écrit :
Hi Joel!
On Thu, 17 Sep 2009, Akim Demaille wrote:
+** Use syntax_error from the scanner?
+This would provide a means to raise syntax error from function
called
+from the scanner. Actually, there is no good solution to report a
+lexical
Le 3 nov. 09 à 05:22, Manjusha Rattihalli a écrit :
Hi,
Please respond to this mail as this info is very urgent.. Pls
redirect it to the right alias if needed.
Your question is not very clear, and you should know that
This is free software; see the source for copying conditions.
Ther
Le 19 déc. 2009 à 06:18, Joel E. Denny a écrit :
> I pushed this to master. The bug does not exist on branch-2.5. The test
> case makes this bug look pretty obscure, and maybe that's right, but I
> really didn't spend much time searching for a simpler test case.
Looks good to me.
> +void
>
Le 17 déc. 2009 à 03:29, Joel E. Denny a écrit :
> The following patch is next. The problem it addresses is that users
> sometimes write semantic actions that manipulate yychar.
Wow, really? What is a typical use of this feature?
Toying with codesearch I have found some ancient versions of G
Le 28 déc. 2009 à 04:51, Joel E. Denny a écrit :
> I'd like to push these patches to branch-2.5. In preparation for a future
> patch, they port some changes from master. I don't believe there are any
> other changes from master that these depend upon, but I'll wait a little
> while for comme
Le 15 déc. 2009 à 00:43, Joel E. Denny a écrit :
> I want assert's output as it can facilitate development and bug reporting,
> so I pushed the following to master, branch-2.5, and branch-2.4.2. I
> decided to simply do `#define aver assert'. I also added gnulib's assert
> module. We can ad
Le 23 nov. 2009 à 19:15, Joel E. Denny a écrit :
Hi all!
> I've only recently begun to understand the difference between @samp and
> @code (because I saw Akim correct some of my poor usage), and I'm not sure
> I completely understand it.
Well, I would not pretend I know the rule :) The one I
Great work Alex!
Le 27 nov. 2009 à 12:21, Joel E. Denny a écrit :
>>> +...@node Named References
+...@subsection Using Named References
>>>
>>
>> I just noticed that almost all sections have "short" node names and somehow
>> more elaborated subsection names. Have I missed something here ?
Le 30 déc. 2009 à 10:57, Joel E. Denny a écrit :
> On Wed, 30 Dec 2009, Joel E. Denny wrote:
>
>> The patch below restores the complaint (as an error not a warning) for the
>> case when a %prec symbol is not defined, but it maintains the complaint
>> for the case when the symbol is a nontermin
Hi Joel,
Le 30 déc. 2009 à 21:08, Joel E. Denny a écrit :
>> There is quite some work here :( We have too many branches alive. I'm
>> sorry I don't help more; making some releases would relieve you from
>> maintaining so many different versions.
>
> I think we should roll 2.4.2 soon. I can d
On Fri, Jan 15, 2010 at 7:52 PM, Joel E. Denny wrote:
> Hi guys,
>
> Sorry for this oversight. I went ahead and pushed this patch to master,
> branch-2.5, and branch-2.4.2 so that I don't forget it before rolling
> 2.4.2.
Thanks Joel. Some day, I hope I (/we) manage to make a first stab at
Biso
Le 2 févr. 2010 à 10:30, Joel E. Denny a écrit :
> Here's an attempt at fixing this. Not yet pushed. I now need to decide
> whether this fix is too much for 2.4.2. If so, I suppose I could just
> comment out the affected test group for 2.4.2, but I'm suspicious that
> there's a race conditi
Le 27 nov. 2009 à 02:12, tys lefering a écrit :
> hi,
> very easy ported the vcg graph output drivers
> from bison-2.3a into the bison-2.4.1 version.
> now there is a choice of graph output to use.
>
> when using 'bison -g parser.y' then it generates
> both dot and vcg graph output and when a fi
Le 10 mars 2010 à 21:25, tys lefering a écrit :
Hi Tys,
> On Wed, March 10, 2010 17:27, Akim Demaille wrote:
>> Now that Graphviz is free software, with nice software available on all
>> the common architectures, what's the point of maintaining VCG output?
> Some notes an
Le 20 mars 2010 à 20:16, Joel E. Denny a écrit :
> I pushed this to branch-2.4.2, branch-2.5, and master. I also pushed a
> v2.4.2 tag, and I regenerated the html manual into CVS.
>
> It bothers me that branch-2.5:ChangeLog and master:ChangeLog now have an
> entry that says "Version 2.4.2" bu
Le 20 mars 2010 à 23:40, Joel E. Denny a écrit :
> Hi Akim,
Hi Joel,
> But that raises another question for NEWS. If Bison ends up like gcc and
> has multiple release series concurrently, the order of releases might be:
> 2.4.2, 2.5, 2.4.3, 2.5.1. Do we sort by version number or release dat
Le 17 mars 2010 à 20:34, Joel E. Denny a écrit :
>> Yes, but I'm no big fan of having several outputs here. Joel might have
>> another opinion. Maybe gnulib could support a factored means to support
>> both outputs. But the xsl-based approach you recently proposed seems a
>> more acceptable
Le 17 mars 2010 à 22:48, tys lefering a écrit :
> Hi Akim,
>
> On Wed, March 17, 2010 17:07, Akim Demaille wrote:
>> complete the VCG tools with a GPL dot-parser.
> Attempting to do that with a manual written parser
> and it is quite difficult, but does already a lot.
I
Le 12 mars 2010 à 01:02, tys lefering a écrit :
> Hello Akim,
Hi Tys,
> The google go language gcc frontend is
> now in gcc svn called gccgo.
>
> Soon it will be in main gcc source tree
> and distributed with gcc installations.
Wow. I didn't know they were there already.
> Are there plans t
Le 5 févr. 2010 à 00:47, Joel E. Denny a écrit :
> Akim, because you've already looked at
> create_pipe_bidi, I figure you might want a chance to review this before I
> push.
FWIW, it's about the same patch that the one I had tried (in branch
candidates/create-pipe-bidi) except that yours i
+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index bf67e12..e8091e3 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2010-03-25 Akim Demaille
+
+ tests: fix 250: parse.error=verbose overflow.
+ * tests/regression.at (parse.error=verbose overflow): Avoid the
+ d
Le 20 janv. 2010 à 17:00, Joel E. Denny a écrit :
Hi Joel,
Trying to reduce a bit my todo stack...
>> On Tirsdag 19 januar 2010, Joel E. Denny wrote:
>>> On Mon, 18 Jan 2010, Akim Demaille wrote:
>>>> If it is not the case (I don't have Bison at
>>>&g
I have pushed the following patch in 2.4.3, 2.5, and master.
* src/graphviz.h: Add missing license notice.
Document.
From c0259969d7a2a82a62a28f04448ce9843046a10d Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Tue, 30 Mar 2010 14:33:58 +0200
Subject: [PATCH] fix comments
it was safe to use it as the graph name. But I'd be happy to
hear other opinions.
Cheers!
From a02797656ed9675eaabfcf9114301f8c7cb45383 Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Mon, 5 Apr 2010 21:30:36 +0200
Subject: [PATCH 1/2] graph: sign the output file.
* src/graphviz.
Le 24 mars 2010 à 17:24, tys lefering a écrit :
>>> And can always create a new custom bison version for
>>> myself with vcg drivers added. only 1 hour work for me.
>> That's an hour you certainly would prefer to spend on something else :)
> It took 10 min. for bison-2.4.2 and just like to do it.
Le 23 mars 2010 à 09:14, Chris Morley a écrit :
> Hi All,
Hi!
> I use Bison to generate a C++ parser using the lalr1 skeleton. I also use a
> custom location class.
>
> I just upgraded a project from using v2.3.1 to v2.4.2 and as I am on Windows
> defines a max macro which breaks std::max n
Le 30 avr. 10 à 23:53, Joel E. Denny a écrit :
Hi Akim,
The only remaining issue I see for 2.4.3 is here:
http://lists.gnu.org/archive/html/bug-bison/2010-04/msg00021.html
That's a patch you were planning to push. If you're ready with it,
please
go ahead. If you don't have time, please
Le 1 mai 2010 à 02:02, Joel E. Denny a écrit :
> Graphviz also supports comments starting with "//", so what do you think
> of the first patch below?
Actually, I knew, and I felt that, provided there's an even distribution of
characters in file names (which is obviously true), it was 256 times
Le 2 mai 2010 à 02:55, Joel E. Denny a écrit :
>> also the graph title will appear in few types of dot
>> output, for example the ps output with 'dot -Tps' as:
>
> I wasn't aware of that. Good point.
>
> What about something like
>
> "LALR(1) Automaton for parser.y"
>
> where LALR(1) could
Le 3 mai 2010 à 07:22, tys lefering a écrit :
> attached patch.txt
> Thanks.
>
Hi Tys,
Could you please send the patch in unified diff format? This is the one we are
used to read. Use diff -u. Thanks!
Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
> think I failed to keep you in CC, please have a look at the archive (it
> should appear in
> http://lists.gnu.org/archive/html/bison-patches/2010-04/th
Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
> think I failed to keep you in CC, please have a look at the archive (it
> should appear in
> http://lists.gnu.org/archive/html/bison-patches/2010-04/th
Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
> think I failed to keep you in CC, please have a look at the archive (it
> should appear in
> http://lists.gnu.org/archive/html/bison-patches/2010-04/th
Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
> think I failed to keep you in CC, please have a look at the archive (it
> should appear in
> http://lists.gnu.org/archive/html/bison-patches/2010-04/th
Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
> think I failed to keep you in CC, please have a look at the archive (it
> should appear in
> http://lists.gnu.org/archive/html/bison-patches/2010-04/th
Installed in master, makes no sense in 2.5.
We need to check that %printer/%destructor are about "existing" type tags.
From f5da8149a27834cbce2839d527f7f34430125de6 Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Thu, 29 Apr 2010 12:35:13 +0200
Subject: tests: fix %printer.
Curren
Installed in master, makes no sense in 2.5.
From 19ad326be4a09a1c7ea6ce8bea5adaf90d1f8fae Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Wed, 14 Apr 2010 18:34:36 +0200
Subject: lalr1.cc: minor refactoring.
* data/lalr1.cc: Don't issue empty namespaces.
---
ChangeLog |
Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
> think I failed to keep you in CC, please have a look at the archive (it
> should appear in
> http://lists.gnu.org/archive/html/bison-patches/2010-04/th
Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
> think I failed to keep you in CC, please have a look at the archive (it
> should appear in
> http://lists.gnu.org/archive/html/bison-patches/2010-04/th
Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
> think I failed to keep you in CC, please have a look at the archive (it
> should appear in
> http://lists.gnu.org/archive/html/bison-patches/2010-04/th
Le 4 mai 2010 à 15:24, Akim Demaille a écrit :
>
> Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
>
>> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
>> think I failed to keep you in CC, please have a look at the archive (it
>>
Le 4 mai 2010 à 15:30, Akim Demaille a écrit :
>
> Le 14 avr. 2010 à 13:19, Akim Demaille a écrit :
>
>> I have installed a first batch of changes in 2.5 and 2.6 to this end. I
>> think I failed to keep you in CC, please have a look at the archive (it
>>
Installed in master only.
From bb9191dd311e4c6d80f8dd12c6a7ce9254404fbc Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Sun, 9 May 2010 23:58:50 +0200
Subject: [PATCH] c++: use YYRHSLOC.
* data/lalr1.cc (YYRHSLOC): New.
(YYLLOC_DEFAULT): Use it.
* data/glr.cc: If
I would like to document %define location_type (and some more tests, and some
more NEWS), but the name is poor. I guess we should make it something like
%define api.location.type. But then, I feel that I was wrong with
api.tokens.prefix. Joel, is the name api.location.type appropriate? Shoul
Le 10 mai 2010 à 10:01, Akim Demaille a écrit :
> Installed in master only.
> From bb9191dd311e4c6d80f8dd12c6a7ce9254404fbc Mon Sep 17 00:00:00 2001
> From: Akim Demaille
> Date: Sun, 9 May 2010 23:58:50 +0200
> Subject: [PATCH] c++: use YYRHSLOC.
>
> * data/lal
From e944aaff36c500c8de9537551fe1aa8458b23fe2 Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Tue, 11 May 2010 21:31:31 +0200
Subject: [PATCH 1/3] doc: please Emacs.
* doc/bison.texinfo (Local Variables): Move this after the
LocalWords, since the latter are looked for in the
I realize that this patch has a stowaway: the section about "YYLLOC_DEFAULT in
C++" was meant to be part of the forthcoming patch. I failed to rebase
properly my patches, sorry about that.
From 27290b603576d04f1d6498b0ca509a84b81f193f Mon Sep 17 00:00:00 2001
From: Akim Demaille
Installed in master. Will be installed in 2.5 too.
From 38435078b14ad063d7bc9e82a7db9bac366b2e65 Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Tue, 11 May 2010 23:51:59 +0200
Subject: [PATCH 3/3] lalrl1.cc: give a chance to user defined YYLLOC_DEFAULT.
* data/lalr1.cc
Le 12 mai 2010 à 10:33, Akim Demaille a écrit :
> Installed in master. Will be installed in 2.5 too.
Done.
> From 38435078b14ad063d7bc9e82a7db9bac366b2e65 Mon Sep 17 00:00:00 2001
> From: Akim Demaille
> Date: Tue, 11 May 2010 23:51:59 +0200
> Subject: [PATCH 3/3] lalrl1.cc: g
The code is already better (it's factored) in 2.5 and master, and does not
trigger GCC warnings. So this is 2.4.3 only.
From a151f354cfd8627b3fb1930bf95d42d7af973af6 Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Wed, 21 Jul 2010 18:10:50 +0200
Subject: [PATCH] Pacify gcc war
Le 24 juil. 2010 à 22:52, Joel E. Denny a écrit :
> On Mon, 3 May 2010, Joel E. Denny wrote:
>
>> That sounds great. It might be this weekend before I roll 2.4.3.
>
> Sorry for the massive delay. But at least we now have an updated license.
> Thanks, Paul and Akim.
>
> I'd like to roll 2.4
parse.error verbose %debug %name-prefix "calc"
%verbose %yacc %parse-param {semantic_value *result} %parse-param {int *count}
(calc.at:729): FAILED (calc.at:729)
From c49784f5f5c0b8a4ffda574e2cf5a1e3e63110ba Mon Sep 17 00:00:00 2001
From: Akim Demaille
Date: Wed, 1 Sep 2010 15
Le 8 oct. 10 à 20:14, Paul Eggert a écrit :
In trying to install a simple pitch to Bison I found that
it didn't bootstrap at all, due to changes to Gnulib in
the past few months. What a hassle. This turned a 15-minute
fix into something that took hours to check.
wow. Thanks for doing it.
Le 4 janv. 2011 à 22:51, Paul Eggert a écrit :
> We can do this by using something like the following:
>
> letter [.abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ_]
> id -*(-|{letter}({letter}|[-0-9])*)
> ref -?[0-9]+|{id}|"["{id}"]"|"$"
>
> and then "id" would be treated consis
Le 4 janv. 2011 à 01:24, Joel E. Denny a écrit :
> Hi,
>
> In my current work on bison.texinfo, I'm finding it tedious to write
> @acronym{...} around every GNU, LR, LALR, IELR, LAC, etc. Lately, it
> seems people are discouraging its usage anyway:
>
> http://lists.gnu.org/archive/html/bug-
hi all!
Le 10 janv. 2011 à 00:24, Joel E. Denny a écrit :
>> So no objections from my side.
>
> Thanks.
>
> I folded in the following correction and then pushed that patch to master
> and branch-2.5.
Good with me too.
Le 24 déc. 2010 à 05:51, Joel E. Denny a écrit :
Hi Joel,
Nice christmas gift you made us! Sorry for the delays, my backlog is, err,
significant :)
> LAC is the last major new feature I had planned for Bison 2.5. Without
> LAC, IELR is guaranteed to behave like canonical LR only for syntact
Le 15 janv. 2011 à 22:50, Joel E. Denny a écrit :
Hi all,
Sorry, it took so long before I read this.
> Sorry, my opinion is that your patch does more harm than good and should
> be backed out. However, I would very much like for Alex and Akim to give
> their opinions.
I subscribe to this op
Le 15 janv. 2011 à 22:50, Joel E. Denny a écrit :
1.
> An identifier can be any sequence of letters, underscores, periods,
> dashes, and digits that does not start with an integer (unsigned or
> negative).
2.
> An identifier can be any sequence of letters, underscores, periods,
> dashes,
Le 20 janv. 2011 à 07:27, Paul Eggert a écrit :
> On 01/19/2011 12:13 AM, Alex Rozenman wrote:
>> it is impossible to obtain an unambiguous grammar with syntax extensions
>> like id '[' c_id ']' without involving the ';' requirement.
>
> Yes, but that's OK; that's what I'm proposing. That is, I
Le 25 janv. 2011 à 04:47, Joel E. Denny a écrit :
> Also, as you probably recall, the reason scan-gram.l has to be so messy in
> order to support omitting semicolons is because Bison-generated parsers
> support only one token of lookahead. However, after 2.5, I'd like to
> propose a mechanism
Le 12 févr. 2011 à 15:32, Joel E. Denny a écrit :
> Below is a series of patches that begin to clean up the manual. I wrote
> them for branch-2.5. I haven't pushed yet. I still need to prepare
> similar patches for master.
Amazing work... I suppose there were many conflicts when ported to
Le 12 févr. 2011 à 15:30, Joel E. Denny a écrit :
> On Sat, 29 Jan 2011, Joel E. Denny wrote:
>
>> On Thu, 27 Jan 2011, Joel E. Denny wrote:
>>
3.
> An identifier can be any sequence of letters, underscores, periods,
> dashes, and digits that does not start with a digit or dash.
>
Le 29 janv. 2011 à 15:49, Joel E. Denny a écrit :
>> I think we should create a Reference section pointing to the various
>> papers on top of which Bison is built.
>
> Thanks, that sounds better than what I was thinking. So, as in an
> academic publication, I suppose we should somehow cite en
Le 20 févr. 2011 à 23:04, Joel E. Denny a écrit :
> Thanks, but how about something simple like the following instead? I
> wrote it against branch-2.5, but it applies cleanly to master. Not yet
> pushed.
That's what I would have done. It's great to see all the improvements you made
to the
Le 20 mars 2011 à 23:17, Joel E. Denny a écrit :
>> On second thought, "full" doesn't answer the question of "which states".
>> That is, we had "all states", "consistent states", and "accepting state".
>> "full states" doesn't make sense. I'm thinking of changing it to "most",
>> but I'll h
Le 28 mars 2011 à 04:56, Joel E. Denny a écrit :
> I feel that -Wnone should affect all warnings. That's how it's currently
> documented, and it seems like a useful feature. I'd like to push the
> following patches to branch-2.5 and master. Any objections?
none ;)
Le 28 mars 2011 à 04:55, Joel E. Denny a écrit :
> To put that another way, -Wall doesn't enable -Werror, so -Wnone shouldn't
> disable -Werror. I'd like to fix that on branch-2.5 and master.
>
> However, I first need to cherry pick a related patch from master to
> branch-2.5 and document tha
Le 28 mars 2011 à 04:58, Joel E. Denny a écrit :
>> Actually, we should probably split -Wconflicts into -Wconflicts-sr and
>> -Wconflicts-rr given that S/R and R/R conflicts are usually considered to
>> be very different levels of severity.
>
> Implemented below, but I still need to add some t
Le 25 juil. 2011 à 00:45, Joel E. Denny a écrit :
> A few years ago, Jim Meyering removed tabs from coreutils source code:
>
> http://lists.gnu.org/archive/html/bug-coreutils/2009-08/msg00219.html
>
> I have long wanted to do the same for bison. Now, while bison development
> is especially s
Hi Joel!
Le 1 août 2011 à 02:51, Joel E. Denny a écrit :
> By the way, I've also been bothered that Bison's test suite defines many
> m4 macros whose names start with `AT_', which violates Autotest's
> namespace. In the skeleton, we avoid `m4_' by using `b4_', so it seems we
> should avoid `A
Le 30 oct. 2011 à 03:25, Tim Landscheidt a écrit :
> Hi,
Hi Tim,
> I hope this list is the right place for this.
>
> In the past few weeks, I started working on "%language
> PHP". You can browse the code at
> https://github.com/scfc/bison-php> (bison's "master" is
> "upstream").
I am very cu
With the current master, I have failures about sched.h, which
should be lib/sched.h. We have too much dependency on the
state of gnulib inside configure.ac. I propose the following
simple change. It is optimistic (i.e., one can easily forge cases
where it would break), but I'm not sure we need t
Le 20 janv. 2012 à 14:17, Jim Meyering a écrit :
>> * configure.ac: Instead of listing gnulib's variables, look for
>> them among AC_SUBST variables.
>
> Nice. That is much more maintainable.
Thanks for the review. I installed it in master. I will install it
in branch-2.5 after I h
I like silent rules _a lot_. They really help see hidden
warnings/messages in the logs, yet it's very easy (pass
V=1 to make) to restore the verbose behavior.
WDYT?
0001-maint-silent-rules.patch
Description: Binary data
Hi Joel, Hi Wolfgang,
>> 247: parse-gram.y: LALR = IELR ok
>
> In your original report, this test group also failed. Do you know what
> the problem was? Maybe you still have the original tests/testsuite.log.
This was recently fixed by Paul Eggert,
http://lists.gnu.org/a
Le 14 janv. 2012 à 01:31, Yuri a écrit :
> Hi bison maintainers,
Hi Yuri,
> The attached patch fixes the CPU problem that these lines in pack_vector
> function caused in certain testcases:
> for (k = 0; ok && k < vector; k++)
>if (pos[k] == j)
> ok = false;
>
> In the ve
Hi Stefano, thanks Paul,
Le 25 janv. 2012 à 20:44, Stefano Lattarini a écrit :
> On 01/25/2012 08:41 PM, Paul Eggert wrote:
>> It may be simplest to wait until Automake 1.11.3 comes out before
>> applying that patch. I don't think this will be long.
> If there are no major problems, 1.11.3 shoul
1 - 100 of 4277 matches
Mail list logo
