or
simple languages I believe it tends to be much less of a hassle to
simply develop the parser by hand instead of forcing Bison to do our
bidding.
Rui Maciel
___
help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
Alfonso Urdaneta wrote:
> resubscribing after a long time off, this list still alive?
Yes, although the traffic is pretty scarce.
Rui Maciel
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
way to reduce it. Please give me an example or
> link. Thanks.
The parser is only there to extract information from a given input. What you
do with the information extracted from that input is only up to you and
doesn't involve the parser in any way.
Rui Maciel
__
Luca Marzolla wrote:
> Use yylineno variable.
> See %option yylineno in Flex:
> http://flex.sourceforge.net/manual/Options-Affecting-Scanner-Behavior.html#
> Options-Affecting-Scanner-Behavior
Thanks, Luca. It was just what the doctor ordered. Thanks!
Best regards
teract with. Is there something else you think should be mentioned?
Weird. That's exactly what I wished for. I don't know if I should be glad that
my wishes have been met or if I should kick myself for not opening my eyes
while RTFM.
Nonetheless, thanks for the help. Kudos!
Rui
How is it possible to make yyerror also report the line where an error was
found?
Thanks in advance,
Rui Maciel
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
n the other hand, it
accepts the following:
%name-prefix = "prefix"
Another aspect which would be nice to have on that part of the manual is a
reference to the implications that option has on the demands it imposes on the
lexer.
Rui Maciel
_
seems to be a bit of a hack.
So, according to your experience, what's the best strategy to parse multiple
versions of a document format?
Thanks in advance,
Rui Maciel
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
ng yy_push_state() and co from
within the bison code?
Handling yy_push_state() directly from bison appears to be a cleaner way of
doing things.
> I agree it also seems bizarre that start conditions are defined in the
> header file, but that yy_push_state is static.
Is it possible th
the gmane newsgroup but I'm not sure they
found their way into the mailing list. Does anyone use gmane to access the
mailing list? If so, what's the best way to post messages to this mailing
list?
Rui Maciel
%{
#define YY_HEADER_EXPORT_START_CONDITIONS
#include
#include &quo
Flex scanner (to get the
> token definitions and so forth). I have no experience with the
> converse.
I've sent an email with all the test project files attached (flex, bison,
makefile).
Rui Maciel
___
help-bison@gnu.org http://lists.gnu.or
Hans-Bernhard Bröker wrote:
> Rui Maciel wrote:
> > Is it possible to set the flex start conditions from within bison?
>
> See "info flex faq unnamed-faq-71".
The article you pointed out suggests that a flex-generated header file would be
cleaner but it's unavai
will
hold the definitions. Unfortunately they are enclosed in a #define statement.
Rui Maciel
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
efine
YY_HEADER_EXPORT_START_CONDITIONS and therefore declare the start condition
symbol.
So, how do we set flex start conditions from within a bison file?
Thanks in advance,
Rui Maciel
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
14 matches
Mail list logo