In a nutshell, give your grammar files a .ym extension instead of .y. Xcode will then run Bison with the necessary magic to support Objective-C. Oddly enough, I found this question because I wanted to do the same thing. I remembered a discussion about it on Apple’s cocoa-dev mailing list, but this question came up … Read more
Same happened to me, it was due to lack of flex and bison. After installing flex and bison, I ran make distclean and ./configure, then it compiled fine.
See here. You can install with brew: brew install bison Then update your scripts or your shell config to use brew’s bison first in your PATH: export PATH=”$(brew –prefix bison)/bin:$PATH” Or export PATH=”/usr/local/opt/bison/bin:$PATH”
The union (%union) defined is not intended to be used directly. Rather, you need to tell Bison which member of the union is used by which expression. This is done with the %type directive. A fixed version of the code is: %{ #include <iostream> int yylex(); void yyerror(const char*); %} %union { char name[100]; int … Read more
The following routines are available for setting up input buffers for scanning in-memory strings instead of files (as yy_create_buffer does): YY_BUFFER_STATE yy_scan_string(const char *str): scans a NUL-terminated string` YY_BUFFER_STATE yy_scan_bytes(const char *bytes, int len): scans len bytes (including possibly NULs) starting at location bytes Note that both of these functions create, return a corresponding YY_BUFFER_STATE … Read more
As for today (2011-04-05, updated 2017-11-29) you will need the lastest versions of: flex-2.5.4a-1.exe bison-2.4.1-setup.exe After that, do a full install in a directory of your preference without spaces in the name. I suggest C:\GnuWin32. Do not install it in the default (C:\Program Files (x86)\GnuWin32) because bison has problems with spaces in directory names, not … Read more
You are probably including windows.h somewhere, which defines macros named max and min. You can #define NOMINMAX before including windows.h to prevent it from defining those macros, or you can prevent macro invocation by using an extra set of parentheses: column = (std::max)(1u, column + count);
If you want an easy way to code parsers, or you are tight on space, you should hand-code a recursive descent parser; these are essentially LL(1) parsers. This is especially effective for languages which are as “simple” as Basic. (I did several of these back in the 70s!). The good news is these don’t contain … Read more
There are some differences between Lex and Flex, but you have to be abusing Lex to run into the problems with Flex. (I have a program which abuses Lex and doesn’t work under Flex, therefore.) This is primarily in the area of input lookahead; in Lex, you can provide your own input code and modify … Read more
Update/warning: This answer may be out of date! One major difference is that ANTLR generates an LL(*) parser, whereas YACC and Bison both generate parsers that are LALR. This is an important distinction for a number of applications, the most obvious being operators: expr ::= expr ‘+’ expr | expr ‘-‘ expr | ‘(‘ expr … Read more