Paul == Paul Hilfinger [EMAIL PROTECTED] writes:
In fact, this issue did get discussed when the GLR skeleton got
introduced, and the language (or lack of it) is, AIR, deliberate on
the part of the lead maintainers at the time. On consideration, I
would prefer that the same terms apply
Sylvain == Sylvain Schmitz [EMAIL PROTECTED] writes:
Paul Hilfinger wrote:
In fact, this issue did get discussed when the GLR skeleton got
introduced, and the language (or lack of it) is, AIR, deliberate on
the part of the lead maintainers at the time. On consideration, I
would prefer
Tim == Tim Van Holder [EMAIL PROTECTED] writes:
Paul Eggert wrote:
Bison version 2.1 has been released.
It would be nice if you added a step
- freeze messages and submit pot files to the TP one week before
release
to the Bison release procedure (or alternatively, make 'submit
Jan == Jan Nabbefeld [EMAIL PROTECTED] writes:
Hello,
I've read on [1]
This [1] was not defined.
about the possibelity off defining a base class for the generated
yy::parser in lalr1 skeleton. Further I noticed that this was
removed from the lalr1 skeleton on December 2004.
That is
Wolfgang == Wolfgang Spraul [EMAIL PROTECTED] writes:
Let's say you have an action that gets an object passed in which
has a destructor. When using YYABORT inside the action, the
destructor for this object is always called. When using YYERROR, it
is never called, i.e. the action needs to
Joel == Joel E Denny [EMAIL PROTECTED] writes:
I prefer that the clean-up *not* happen automatically for either
YYABORT or YYERROR -- as in GLR parsing. This would allow for a
simple consistent rule: if the user's semantic action executes,
then the user's semantic action is responsible
Paul == Paul Eggert [EMAIL PROTECTED] writes:
I installed the following patch, which I hope fixes the YYUSE problems
discussed in the %destructor feedback thread.
2005-12-09 Paul Eggert [EMAIL PROTECTED]
Cleanups so that Bison-generated parsers have less lint.
* data/c.m4
Hal == Hal [EMAIL PROTECTED] writes:
Hi
I hope this is the right list to ask. I have a problem where I really can't
work out what I could be doing wrong -- so I am beginning to wonder whether
it's a bison bug.
It is. And it is fixed in 2.1.
Joel == Joel E Denny [EMAIL PROTECTED] writes:
On Wed, 7 Dec 2005, Akim Demaille wrote:
Joel == Joel E Denny [EMAIL PROTECTED] writes:
On Wed, 7 Dec 2005, Akim Demaille wrote:
Paul == Paul Eggert [EMAIL PROTECTED] writes:
Why can't we simply rewrite the code so
I'd like to see 2.2 out in January if we can, so I'd like to close
this file. Do we agree that:
- we desire a warning about typed $n not used in the actions. A
simple macro that ignores its argument suffice to avoid the
complaints.
- we desire that in all the skeletons no $n is ever freed
Bob == Bob Rossi [EMAIL PROTECTED] writes:
I would contact the author, if I could figure out how to get the
email address. Also, I'm not solely reling on the original
poster. I would be willing to do the work myself with a little
guidance. I've already contributed to GDB's MI interface,
Akim == Akim Demaille [EMAIL PROTECTED] writes:
For the records, I have at hand a printout of a message from Odd Arild
Olsen that details his implementation of a push parser, but I don't
have his address...
If I had read until the end the print out, I would have found the
following url
the bit of code that is wrong.
I installed the following.
Index: ChangeLog
from Akim Demaille [EMAIL PROTECTED]
YYACCEPT, YYERROR, and YYABORT, as user actions, should not
destroy the RHS symbols of a rule.
* data/yacc.c (yylen): Initialize to 0.
Keep its value
Paul == Paul Eggert [EMAIL PROTECTED] writes:
These two patches are still pending in this area.
http://lists.gnu.org/archive/html/bison-patches/2005-12/msg00048.html
http://lists.gnu.org/archive/html/bison-patches/2005-12/msg00049.html
The former is more important. I'd like Paul H.'s
Dempe == Dempe Dempe [EMAIL PROTECTED] writes:
Hi,
I MUST use bison to generate C++ classes and compile it in MSVC.
I started compiling the basic example of the Calc++ -- C++ Calculator.
It works perfectly using gcc, but using MSVC in the declaration
class position
{
public:
Le 20 févr. 06 à 15:07, Akim Demaille a écrit :
Don't use YYPRINT, see %printer in the recent docs.
Err, on second thought, it is not yet documented :) For instance
%printer { fprintf (stderr, %d, $$); } integer [etc...]
@$ is also available there, denoting the location of the symbol
Le 21 févr. 06 à 22:04, Henrik Sorensen a écrit :
On Tuesday 21 February 2006 08.27, Akim Demaille wrote:
Le 20 févr. 06 à 15:07, Akim Demaille a écrit :
Don't use YYPRINT, see %printer in the recent docs.
Err, on second thought, it is not yet documented :) For instance
%printer { fprintf
Le 1 févr. 06 à 10:54, Daniel Wasserhaus a écrit :
Hello,
Is it possible to build an one-pass parser with bison??
Oris it possible to make its parser jump (discard) from a '{'
to another
'}' without executing the sentences that are into those brackets??
sometimes I really feel like writing rules like this:
Rule: (A | B) C D
Which would allow A C D or B C D. What is the reason to that such
constructs
are not possible?
Simply because nobody has implemented it. I think some grads at
Berkeley made a Bison version with such constructs.
Le 7 mars 06 à 21:22, Hans Aberg a écrit :
Interesting. So who knows, it will be interesting to see if
something pops up
at somepoint.
If somebody gets interested in implementing it. It should not be
too difficult, at this point, as Bison itself has a .y grammar,
making grammar
The LALR(1) algorithm that Bison uses, was developed in this
vein; Bison probably ought to also have LR(1) these days, which
may expand the parser size several times, but would not matter on
todays computers.
About LR(1), I recently found out menhir
Marcus == Marcus Holland-Moritz [EMAIL PROTECTED] writes:
Hi,
I'm using bison for a C parser [1], for which I'm currently rewriting
the part that parses expressions.
While being at it, I wondered if it's possible to reuse a certain part
of a bison generated parser, e.g. by setting a
Le 9 mai 06 à 00:31, Satya Kiran a écrit :
hi,
I am a grad student studying at the University of Illinois at Chicago.
I wanted to contribute to Bison through the Google Summer of Code
program and I prepared this proposal.
But somehow in the last minute my university tells me I am not
Le 3 juin 06 à 02:40, Satya Kiran a écrit :
hi Akim,
Can you demystify muscle_table and Obstacks for me please?; what is a
muscle_table used for? I get a hazy idea of Obstacks, but I am not
clear what this kind of data structure is for.. how does it work and
why is it there..
Consider
Le 29 juil. 06 à 07:13, Joel E. Denny a écrit :
+ Clean up handling of %destructor for the end token (token 0).
Nice patch. Since we are making BOF and EOF more like
regular tokens, we might be able to simplify the skeletons
even further by attaching the initial-action as a regular
Le 21 août 06 à 20:42, Joel E. Denny a écrit :
On Sun, 20 Aug 2006, Frans Englich wrote:
Any chance that %defines can be changed to also allow the name to be
explicitly specified?
I'm not sure why %defines and -d and are different from --defines, -o,
--output, and %output. Reading the -d
Frans == Frans Englich [EMAIL PROTECTED] writes:
What exactly does it do, it allows one to at runtime customize the
message Bison uses for a token(and perhaps even terminal?)? For
example, that instead of that Bison says Unexpected numeric
literal one can make it say Unexpected '2.3',
Frans == Frans Englich [EMAIL PROTECTED] writes:
I guess one would have to invent a different print system for
that. Perhaps those error printers would return a heap allocated
char string, which the caller(the bison generated parser) is
responsible for de-allocating.
That's very
Frans == Frans Englich [EMAIL PROTECTED] writes:
On Friday 15 September 2006 08:43, Akim Demaille wrote:
Frans == Frans Englich [EMAIL PROTECTED] writes:
I guess one would have to invent a different print system for
that. Perhaps those error printers would return a heap allocated
Tim == Tim Van Holder [EMAIL PROTECTED] writes:
I don't see how _bison_ can do this with any accuracy
Well, with enough insight on locations, I don't see why it couldn't.
Of course it requires changes. One possibility is the one you
mention, which is quite tractable for small files, but
Hans == Hans Aberg [EMAIL PROTECTED] writes:
[Just passing by, no time for more :( ]
It was before I recalling you showing up on the list. Probably Bug-
Bison. Perhaps Akim or Paul can inform the truth about $0.
I did suggest it would be nice to be able to name them, and actually
to
GDA == Geoffrey D Alexander [EMAIL PROTECTED] writes:
However, I did notice a slowdown of 5 to 20 percent in the C++ parser.
Also, the C++ parser shows an increase of 10 to 15 percent in the number
of memory allocation as reported by valgrind.
Is this a known problem? Are there plan to
HA == Hans Aberg [EMAIL PROTECTED] writes:
One idea I have, is to create a core language with the possibility to
translate into several languages. The point is that the parser needs
a rather limited set of language features. This is still, though, not
a very easy one.
ISTR that
S == Satya [EMAIL PROTECTED] writes:
Hello!
I am looking at implementing the XML *. output in Bison this summer.
The one thing I did not understand on the project ideas page
(http://www.gnu.org/software/soc-projects/ideas.html) is
Define an XML grammar for Bison reports
Implement
MK == Max Katsev [EMAIL PROTECTED] writes:
Hello!
I'm interested in applying for GSoC for extending Bison to other languages.
But I'd like to ask some questions first:
1. List of languages. I have strong knowledge of C/C++, Java, Pascal
and base knowledge of C#, python, perl.
I found
Le 1 avr. 07 à 06:46, Joel E. Denny a écrit :
On Fri, 30 Mar 2007, Akim Demaille wrote:
- first, design a true AST for Bison
something to represent the grammar we read. We have more or less
something like this in Bison, but much work is done on it, it's not
faithful to the entry, it's
We definitely should create a branch for that.
CVS branching gives me the willies.
:) I didn't know that idiom, but its sound and the image
it creates in my mind are quite explicit :)
I wish we had a Subversion repository instead of CVS :(
Me too.
I see that Gnulib is trying Git, so
WP == Wojciech Polak [EMAIL PROTECTED] writes:
Hello,
I'd like to inform you that the XML Automaton Report task has
been completed, including the definition of an XML grammar,
implementation in production, and two XSLT transformations.
Please visit
Le 29 sept. 07 à 04:06, Sebastian Pipping a écrit :
Hello Bison people!
I noticed two things with %prefix when combined
with a C++ parser that might be bugs:
(1) %prefix=abc renames function yylex to abclex
instead of putting it in namespace abc.
Well, that was on purpose, to match
Le 30 sept. 07 à 09:00, Joel E. Denny a écrit :
foo::, etc.?
This seems like an error to me.
Sure! But who should catch it? Should we accept a leading ::?
Other than that, isn't it just a matter of splitting on ::? Am I
forgetting something?
No, I don't think you do, it's just that
Le 8 oct. 07 à 12:10, Joel E. Denny a écrit :
Improve C++ namespace support.
Impressive work. Your m4fu is quite mature. How about
maintaining Autoconf? ;)
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
Le 8 nov. 07 à 10:49, Richard Gill a écrit :
Anyone has an idea ?
http://www.gnu.org/software/bison/manual/html_mono/bison.html#Strings-are-Destroyed
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
Le 30 nov. 07 à 12:27, Saurabh Bhatnagar a écrit :
Sure.
I tried and did not get that error simply because the memset coed
was not
there in v2.3.
However to use this we need to make sure that it suns in all supported
platforms.
Can you furnish a list? (32 and 64 bit)
Maybe someone can, I
Le 4 déc. 07 à 18:42, Saurabh Bhatnagar a écrit :
Hi Akim,
From http://gnuwin32.sourceforge.net/packages/bison.htm I don't see
v2.3 ?
We need to have the same version for all platforms supported.
You'll have to try to install it by yourself. Take
the tarball, read README and INSTALL.
Sam == Samuel Tardieu [EMAIL PROTECTED] writes:
Hi.
I've updated Bison enlistments on ohloh.net to point onto the git
repository instead of the CVS one. You must reclaim ownership of your
commits if you use this site.
By the way, congratulations on the conversion process: the use of a
Le 21 nov. 08 à 13:50, 山东 a écrit :
bash 1.05
yylex()in parse.y is maked with flex?
i don't see lex.l in the directory bash\.
This mailing list is about getting help with Bison, not with packages
using Bison.
___
help-bison@gnu.org
MK == Matthias Kramm [EMAIL PROTECTED] writes:
state 1
4 EXPRESSION: T_IDENTIFIER . '(' EXPRESSION ')'
5 | T_IDENTIFIER . [$end, T_IDENTIFIER, ';', '(', ')', ++,
--, '+', '-', '/']
'(' shift, and go to state 5
'(' [reduce using rule 5 (EXPRESSION)]
Le 1 déc. 08 à 13:02, Wouter Sieburgh a écrit :
Hi
I've got a problem building bison 2.*:
Making all in src
make[2]: Entering directory `/develop/devroot64/bison-2.4/src-
bison-2.4/src'
/bin/sh ../build-aux/ylwrap parse-gram.y y.tab.c parse-gram.c y.tab.h
parse-gram.h y.output
Le 20 janv. 09 à 21:53, Alexander Sorockin a écrit :
Hi,
Has anyone besides me noticed that $n with n zero or negative always
triggers a $n ... has no declared type error when a %union is used?
And it's normal: since you are looking deep in the stack, Bison cannot
figure out (in the
Le 28 avr. 09 à 20:55, Danny Backx a écrit :
On Tue, 2009-04-28 at 14:46 -0400, Joel E. Denny wrote:
On Tue, 28 Apr 2009, Danny Backx wrote:
I didn't recognize the significance of this earlier. If the token
STACKSIZE is conflicting with a system header in MacOS, perhaps a
better
fix is to
Le 2 mai 09 à 11:21, Samkit Jain a écrit :
When I checked the states generated by the parser, I found that
there is a
difference in the way $default and $end are created for some states.
Can someone please tell me basic principle behind $end and $default
terminal
symbols.
$default is
Le 27 mai 09 à 10:32, Vincent Zweije a écrit :
In short, I see no problem with this union at all as bison uses it,
semantics-wise, but it is unfortunate that you cannot put your own
classes in there in general.
You will be able to do that in Bison 2.6. A preview is available at
Le 3 juin 09 à 08:35, Henrik Sorensen a écrit :
On Tuesday 02 June 2009 22.27:11 Kynn Jones wrote:
Hi. I'm working with Bison (and Flex) for the first time, and it's
rough
going.
good luck ... we have all been there:-)
Not sure I would have started with the locations though.
This topic
Le 23 juin 09 à 20:18, Akim Demaille a écrit :
Le 21 juin 09 à 22:46, Michiel Helvensteijn a écrit :
It's now 6 years and a bit later. Has this problem been solved in
Bison in the
mean time? Because I can not even find a mention of this in the
manual.
Not, it has not been solved
Le 26 juin 09 à 00:20, Paul Hilfinger a écrit :
Has anyone considered adding extended BNF to Bison? I refer to things
like
A. p : a? ;
B. p : a ( b | c ) d ;
C. p : a ( ',' a )*
D. p : a+
and so forth.
Hi Paul,
Yes, this has been considered several times, but each
Le 25 août 09 à 12:19, Rui Maciel a écrit :
Is it possible to set the flex start conditions from within bison?
I've set a couple of lexer start
conditions in the flex file and added yy_push_state() to the bison
file, which already includes a flex-
generated header. Nonetheless, the compiler
Le 25 août 09 à 13:53, Rui Maciel a écrit :
Akim Demaille wrote:
AFAIK, Flex does not generate a header file with its definitions such
as start conditions, so you probably need to write a small wrapper
around flex that extracts it from the generated scanner *.c file.
Then, from the grammar
Le 26 août 09 à 12:11, Rui Maciel a écrit :
Akim Demaille wrote:
Can you show the content of this file? Can you also show where you
include it in your Bison file? Maybe you include the flex header
from
the bison and vice versa, which probably does not work as expected.
Usually you
Le 27 août 09 à 20:52, Rui Maciel a écrit :
I don't know what Flex you use, but using 2.5.35 it does not compile:
you're using push_state, which is static in the scanner.c file, from
the parser.c file.
Yes, that's the most recent SNAFU I stumbled on. Yet, it only goes
that far if I add to
Le 29 août 09 à 04:36, Daniel Olson a écrit :
Hey, I want to be able to run a Bison output file in another
project, but I don't know how. What I think I need to do is A: set a
string to be parsed; B: parse that string. I want to do all of that
from inside a C file, how would I go about
Le 7 sept. 2009 à 20:23, Akim Demaille a écrit :
Le 7 sept. 2009 à 19:48, Derek M Jones a écrit :
Flex Bison is now available (17 years more up to date)
http://oreilly.com/catalog/9780596155971/
Gee, I wish the Bison maintainers were consulted...
My bad, Joel knew about this, being
Le 21 janv. 2010 à 15:06, 魏佳 a écrit :
Hello Every one,
I have a problem with bison, please help me.
How do I add friend class CSV to c++ parser file that was maked by bison?
for example
csv_parser.ypp
...
%define parser_class_name csv_parser
...
I want get
class csv_parser
Le 29 janv. 2010 à 03:11, Aurelien Tran a écrit :
I know that this is the general way to do this but the lexer is in fact an
external module that I cant modify. I would like to avoid rewriting all the
token and their value in another file. If need to I will but I would to
avoid it in order
Le 12 janv. 2010 à 04:17, Peng Yu a écrit :
In Levine' flex bison book, it mentioned As should be apparent by
now, the C++ support in bison is nowhere near as mature as the C
support,... on page 241 (Chapter 9).
Well, one of the two has been existing for about thirty years :)
I'm still
Le 7 mars 2010 à 03:05, Robert Hollencamp a écrit :
I made an example of using Flex and Bison together in C++ and was wondering
if you guys could provide some feedback. Despite the C++ interface being
'experimental' I found it works out pretty good after you figure it out.
Le 19 mai 2010 à 17:55, Krystian Kuczek a écrit :
Hello,
I have program which works on bison 2.3 but do not work on 2.4.1 version.
In version 2.3 in header file i have defines for all tokens i version 2.4.1
i do not have it, and my program do not work!
Is it possible to make bison, to
Le 21 juil. 2010 à 23:15, Panayiotis Karabassis a écrit :
Hi!
Well, it turns out it was a missing YYSTYPE definition from the parser file.
Thus defaulting to int and having yystate accidentally overwritten on
updating yylval. A difficult bug.
I might be missing something, but I don'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
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 see
Le 4 mars 2011 à 08:20, Adam Smalin a écrit :
Hi
Did you specify %debug? Did you set yydebug to true? You don't get any
traces, or just not the ones from the %printer?
Also, pay attention that the traces are sent to stderr, and you're
outputting onto stdout, so they will not appear
hi all,
I would really like to know more about your uses of Bison. What kind of use
can require these tables?
Cheers,
Akim
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
___
help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
Le 24 mai 2011 à 20:32, Sergey Klimkin a écrit :
Hi!
Hi!
Trying to find information about C++ exceptions in semantic actions, with no
results.
Is there any Bison %Decl which allows to move parse stack outside yyparse(),
to destroy a stack values after an exception was thrown within
Le 23 juil. 2011 à 20:17, uclacasey a écrit :
Perhaps is there any way to get feedback from the parser? For example, if it
is about to output a specific error message, I could intercept that error
message, revert, and pass a different token?
p.s: if anything sounds outlandish, it's
Le 25 juil. 2011 à 16:22, Ludovic Courtès a écrit :
However, with a pure API, I don’t see how to get yyresult back from user
code? The code snippet in the manual pushes tokens but never asks for
the result.
If you dive into the generated code, you might find something useful, but
certainly
Le 24 août 2011 à 10:09, Sieburgh,Wouter a écrit :
Hi
I had built a bison, and installed it is a specific directory. That was
OK, as expected.
Later on, I had to move it, but now I'm getting messages like:
cannot open file xxx/bison-2.4/share/bison/m4sugar/m4sugar.m4
Is there a
Le 24 août 2011 à 15:21, Sieburgh,Wouter a écrit :
Hi Akim
If I cannot move it, it means that I will not be able to build bison (in
various versions) and then give those installations to my customers (as a
convenience), unless they copy it in exactly the same path as I built it, am
I
Le 10 janv. 2012 à 01:02, Juergen Schumacher a écrit :
sorry for bothering anybody,
Hi Juergen,
You're not bothering anybody :)
i am trying to c++ parse an include file with flex 2.5.35 and bison 2.3 on a
mac os x snow leopard installation - everything without include file works
Le 13 janv. 2012 à 16:03, Csaba Raduly a écrit :
Hi,
Hi Csaba,
Bison 2.3 used to write the prologue into the definitions file (the header)
Bison 2.4 seems to have changed this and now writes the prologue into
the parser implementation file. This has created a problem for me
because the
Le 3 nov. 2011 à 07:45, thiru ramakrishnan a écrit :
Hello,
Hi Thiru,
I just started using Bison 2.5 (on Ubuntu 9.04 - the Jaunty Jackalope).
I get the error referred to above. I've looked in help-bison Archives and
also searched on the Web for rpl_fprintf but don't find any info.
Le 16 mars 2012 à 06:17, gccbison a écrit :
Is this book being updated for GNU BISON Software version 2.5+ ?
Yes, as you can see, I am updating the document :)
I too was surprised that it's only 1.875 :(
But it will probably be for 2.6.
___
Hi Hans, Hi Victor
Le 26 mars 2012 à 09:59, Hans Aberg a écrit :
Forwarded messages; replies please cc Victor.
Victor: do you have M4 installed?
Well, according to his message, he has.
Hans
Begin forwarded message:
From: Victor Wilden vwil...@informatik.uni-bremen.de
Subject: Re:
Le 10 mai 2012 à 02:57, Brian a écrit :
You can specify the names of the generated source (output) and header
(defines) files. Is there a way to specify the extension and location
of the c++ bison interface generated files (location.hh, position.hh
and stack.hh)? Bison version 2.4.
hi
Le 16 mai 2012 à 16:51, Wei Song a écrit :
Hi,
Hi!
Just have used Bison for several months.
I have two bison parsers in one project and for some reasons the header files
of both parsers are included in one cpp code.
Different namespace names are used, therefore, these two parsers do
Le 21 mai 2012 à 11:34, Akim Demaille a écrit :
Le 16 mai 2012 à 16:51, Wei Song a écrit :
Hi,
Hi!
Just have used Bison for several months.
I have two bison parsers in one project and for some reasons the header
files of both parsers are included in one cpp code.
Different
Le 21 mai 2012 à 14:42, Akim Demaille a écrit :
lalr1.cc: extract stack.hh.
To make merging easier in master.
lalr1.cc: improve Doxygen documentation.
To include the prefix part in the \file directive.
skeletons: remove support for unused directive.
Something that should never have been
Le 21 mai 2012 à 14:42, Akim Demaille a écrit :
lalr1.cc: extract stack.hh.
To make merging easier in master.
lalr1.cc: improve Doxygen documentation.
To include the prefix part in the \file directive.
skeletons: remove support for unused directive.
Something that should never have been
Le 21 mai 2012 à 14:42, Akim Demaille a écrit :
lalr1.cc: extract stack.hh.
To make merging easier in master.
lalr1.cc: improve Doxygen documentation.
To include the prefix part in the \file directive.
skeletons: remove support for unused directive.
Something that should never have been
Le 21 mai 2012 à 14:42, Akim Demaille a écrit :
lalr1.cc: extract stack.hh.
To make merging easier in master.
lalr1.cc: improve Doxygen documentation.
To include the prefix part in the \file directive.
skeletons: remove support for unused directive.
Something that should never have been
Le 21 mai 2012 à 15:33, Stefano Lattarini a écrit :
Hi Akim. I'm really not knowledgeable enough to comment on this
patch proper, but I have a nit about quotation usages ...
On 05/21/2012 02:56 PM, Akim Demaille wrote:
-** liby is no longer asking for rpl_fprintf on some platforms
Le 21 mai 2012 à 15:41, Hans Aberg a écrit :
On 21 May 2012, at 11:34, Akim Demaille wrote:
Is there a better way to do it?
This is indeed a problem. I'm sure what the best way to
address this is. In addition, in some cases, creating the
files location.hh, stack.hh etc. is more
Le 21 mai 2012 à 16:30, Stefano Lattarini a écrit :
it's only NEWS.
Are you sure it is worth to convert also older NEWS entry to the new
quoting format?
Yes, I prefer. That's just more consistent.
Personally, I'd use for sentences or quasi-sentences, and '' for
stuff like options,
Le 21 mai 2012 à 14:56, Akim Demaille a écrit :
This is the patch that really computes the header guards.
From eb76fadde9c5a3b23dc6761ddd4d267a6e7c3965 Mon Sep 17 00:00:00 2001
From: Akim Demaille a...@lrde.epita.fr
Date: Mon, 21 May 2012 14:21:51 +0200
Subject: [PATCH 4/4] c++: compute
Le 21 mai 2012 à 17:55, Hans Aberg a écrit :
Is there any reason to not put all stuff that is public in the parser header?
This would eliminate the need for any additional header files.
That's the plan for those that need not be public.
location.hh is different: you may use it for your
ASTs
Le 21 mai 2012 à 18:27, Hans Aberg a écrit :
On 21 May 2012, at 18:17, Akim Demaille wrote:
Le 21 mai 2012 à 17:55, Hans Aberg a écrit :
Is there any reason to not put all stuff that is public in the parser
header? This would eliminate the need for any additional header files.
That's
Le 21 mai 2012 à 16:00, Akim Demaille a écrit :
From 6b1a80c331c9d01ae63587c27723d8864222f176 Mon Sep 17 00:00:00 2001
From: Akim Demaille a...@lrde.epita.fr
Date: Mon, 21 May 2012 15:52:17 +0200
Subject: [PATCH 1/5] news: convert to double quotes.
* NEWS: Convert from `quoted' to quoted
Le 21 mai 2012 à 14:54, Akim Demaille a écrit :
From 0e931dcd2eee03611ca980ed0d7805d045d3438c Mon Sep 17 00:00:00 2001
From: Akim Demaille a...@lrde.epita.fr
Date: Mon, 21 May 2012 11:40:42 +0200
Subject: [PATCH 2/4] lalr1.cc: improve Doxygen documentation.
* data/location.cc: Qualify
The Bison team is very happy to announce the forthcoming release
of Bison 2.5.1, which addresses quite a few issues from Bison 2.5.
Here are the compressed sources:
ftp://alpha.gnu.org/gnu/bison/bison-2.5.1_rc2.tar.gz (2.7MB)
ftp://alpha.gnu.org/gnu/bison/bison-2.5.1_rc2.tar.xz (1.5MB)
Le 26 juin 2012 à 13:23, Timothy Madden a écrit :
Hello
Hi!
I wrote a grammar file for an approximation of the php language (with the
purpose of adding braces to single-statements under if, for, while, but that
is not included yet), that simply outputs the found tokens back to an output
Le 27 juin 2012 à 08:00, Akim Demaille a écrit :
For instance, you have:
state 88
1 t_comment_or_whitespace: . T_WHITESPACE
2| . T_COMMENT
3 plain_comment_or_whitespace: . t_comment_or_whitespace
4
1 - 100 of 428 matches
Mail list logo
