| Port details |
- bison175 A parser generator from FSF, (mostly) compatible with Yacc
- 1.75_2 devel
 =0      1.75_2Version of this port present on the latest quarterly branch. - There is no maintainer for this port.
- Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
- Port Added: 2005-09-02 08:07:48
- Last Update: 2005-09-04 18:33:15
- SVN Revision: UNKNOWN
- License: not specified in port
- Description:
- Bison is a tool used to write parsers, such as the parser for GNU cc.
It is similar to Yacc, which is included in the base FreeBSD system.
The main difference between Bison and Yacc that I know of is that
Bison supports the @N construction, which gives you access to
the starting and ending line number and character number associated
with any of the symbols in the current rule.
Also, Bison supports the command `%expect N' which says not to mention
the conflicts if there are N shift/reduce conflicts and no reduce/reduce
conflicts.
The differences in the algorithms stem mainly from the horrible
kludges that Johnson had to perpetrate to make Yacc fit in a PDP-11.
Also, Bison uses a faster but less space-efficient encoding for the
parse tables (see Corbett's PhD thesis from Berkeley, "Static
Semantics in Compiler Error Recovery", June 1985, Report No. UCB/CSD
85/251), and more modern technique for generating the lookahead sets.
(See "Efficient Construction of LALR(1) Lookahead Sets" by F. DeRemer
and A. Pennello, in ACM TOPLS Vol 4 No 4, October 1982. Their
technique is the standard one now.)
cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- No installation instructions:
- This port has been deleted.
- PKGNAME: bison
- Flavors: there is no flavor information for this port.
- distinfo:
- There is no distinfo for this port.
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- gm4 : devel/m4
- Runtime dependencies:
-
- gm4 : devel/m4
- Library dependencies:
-
- intl : devel/gettext
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- N/A
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
As an Amazon Associate I earn from qualifying purchases.
