just
should just give permissions away without authentication - I didn't know he was
asking for that. I just thought it was help - the first thing I thought was,
ok, let's start giving suggestions and guiding feedback on how to move forward.
On Sat, Aug 18, 2018 at 12:24 PM Laura Morales
ow that's what I thought. Some volunteer just came in with their valuable
time and got turned away. GNU is a free software organization - part of their
life blood is volunteers. Just because someone doesn't have a background in
that particular thing doesn't mean they should be dismi
Is this sarcastic? Is this a passive-aggressive way to say something? I don't
really understand the message.
Sent: Saturday, August 18, 2018 at 9:01 AM
From: "Kenneth Adam Miller"
To: a...@lrde.epita.fr
Cc: help-bison@gnu.org, james@pentest.nz
Subject: Re: Co-Maintainer
Yeah, we just hav
I'm looking at this example http://esr.ibiblio.org/?p=6341 which is using these
slightly different instructions
%define api.pure full
%lex-param {yyscan_t scanner}
%parse-param {yyscan_t scanner}
and then add another parameter to handle the output
%define api.pure full
%lex-param {yyscan_t scan
- if I want multiple parsers, I *must* use prefix change
- the purpose of a pure/reentrant parser is to encapsulate globals such that I
can call the same parser multiple times and avoid conflicts or race conditions
correct? Is this basically the bottom line?
I thought reentrancy was a substitute
Thanks a lot Alex, this works great.
There is one more thing that I'd like to do. I'd like to have multiple parsers
available in the same codebase, such that I can invoke parser1() or parser2()
or parser-n(), and in turn get some data structure back depending on the parser
I called. Just as an e
I have this simple grammar which basically simply split symbols at white space
%{
#include
#include
%}
%output "parser.c"
%defines "parser.h"
%union { char *str; }
%token WORD
%start Input
%%
Input
: WORD { printf("word: %s\n", yylval.str); }
| I
When I run Bison to generate the parser (.c and .h files), the new files have
extensions ".tab.c" and ".tab.h". What's the meaning of this ".tab" thing and
how can tell Bison not to append it?
___
help-bison@gnu.org https://lists.gnu.org/mailman/listin
Is there somewhere an archive of readily-available grammars that I can reuse
instead of re-writing them from scratch? For example grammars to build parsers
for csv, tsv, ini, json, yaml, c, javascript, java xml, etc.?
___
help-bison@gnu.org https://lis
