bisonc++ 6.08.00-1 source package in Ubuntu
Changelog
bisonc++ (6.08.00-1) unstable; urgency=medium * New upstream version 6.08.00 repaired the (too strict) %prec specification. -- Frank B. Brokken <email address hidden> Sun, 24 Mar 2024 12:30:27 +0100
Upload details
- Uploaded by:
- Frank B. Brokken
- Uploaded to:
- Sid
- Original maintainer:
- Frank B. Brokken
- Architectures:
- any all
- Section:
- devel
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Noble | release | universe | devel |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
bisonc++_6.08.00-1.dsc | 2.0 KiB | 1817bcb70532c28d094d4338aa56ad694dae1f766e56a1f0b57b34be77e55c67 |
bisonc++_6.08.00.orig.tar.gz | 533.8 KiB | f9ae4d875bebb0a79f2958b12a07037cf63216a7ab27934af2fe3d7b14d5c5b9 |
bisonc++_6.08.00-1.debian.tar.xz | 13.5 KiB | 62e45c13933e51a16c52dfb8be00491f69ccf4a9a8cf224a9dab0efad0875cf6 |
Available diffs
- diff from 6.07.00-1 to 6.08.00-1 (36.8 KiB)
- diff from 6.07.00-1build1 (in Ubuntu) to 6.08.00-1 (37.1 KiB)
No changes file available.
Binary packages built by this source
- bisonc++: Bison-style parser generator for C++
Bisonc++ was designed after `bison++', created by Alain Coetmeur. Bisonc++
adds to bison++ a cleaner class-design, using a base-class to communicate
lexical tokens to a lexical scanner.
.
Since bisonc++ generates the parser class as well as the parsing
function. The class can easily be provided with additional members without
needing polymorphic functions. Consequently, classes generated by bisonc++
have no virtual members and actually have but one public member: parse(),
replacing the old-style bison and bison++ yyparse() function.
.
Bisonc++ offers many options, among which an option to define classes
generated by bisonc++ in a separate namespace. This allows developers to
define additional symbols, even outside of the class generated by bisonc++,
without encountering name-collision problems. With bisonc++, artificial means
to prevent name-collisions, like bison and bison++'s yy-convention are not
required anymore when using bisonc++. Bisonc++ merely generates C++ code. If
C code is required, bison should be used. Bisonc++'s grammar requirements are
highly compatible with bison's requirements, so converting a bison grammar
into a bisonc++ grammar should be fairly simple.
.
In addition to the bisonc++ parser generator itself and several skeleton
files, the package contains an extensive man-page, a full manual rewritten
after the original bison manual, and several examples.
.
Some history: Bisonc++ versions 0.98 is a complete rewrite of an LALR(1)
parser generator, as described in Aho, Sethi and Ullman's (1986) book
`Compilers' (a.k.a. the `Dragon Book'). Version 0.98 was completed in May
2005. Another major rewrite was completed one year later, May 2006, resulting
in version 1.00.
- bisonc++-dbgsym: debug symbols for bisonc++
- bisonc++-doc: Bison-style parser generator for C++ documentation
Bisonc++ was designed after `bison++', created by Alain Coetmeur. Bisonc++
adds to bison++ a cleaner class-design, using a base-class to communicate
lexical tokens to a lexical scanner.
.
Since bisonc++ generates the parser class as well as the parsing
function. The class can easily be provided with additional members without
needing polymorphic functions. Consequently, classes generated by bisonc++
have no virtual members and actually have but one public member: parse(),
replacing the old-style bison and bison++ yyparse() function.
.
Bisonc++ offers many options, among which an option to define classes
generated by bisonc++ in a separate namespace. This allows developers to
define additional symbols, even outside of the class generated by bisonc++,
without encountering name-collision problems. With bisonc++, artificial means
to prevent name-collisions, like bison and bison++'s yy-convention are not
required anymore when using bisonc++. Bisonc++ merely generates C++ code. If
C code is required, bison should be used. Bisonc++'s grammar requirements are
highly compatible with bison's requirements, so converting a bison grammar
into a bisonc++ grammar should be fairly simple.
.
In addition to the bisonc++ parser generator itself and several skeleton
files, the package contains an extensive man-page, a full manual rewritten
after the original bison manual, and several examples.
.
Some history: Bisonc++ versions 0.98 is a complete rewrite of an LALR(1)
parser generator, as described in Aho, Sethi and Ullman's (1986) book
`Compilers' (a.k.a. the `Dragon Book'). Version 0.98 was completed in May
2005. Another major rewrite was completed one year later, May 2006, resulting
in version 1.00.
.
This package provides the supplemental documentation for Bisonc++.