Ubuntu
bisonc++ package

bisonc++ 4.04.01-1 source package in Ubuntu

Changelog

bisonc++ (4.04.01-1) unstable; urgency=low


  * New upstream release. 
    - Streamlines path specifications for generated files.

  * Removed the explicit compiler version (4.7) from debian/rules

 -- Frank B. Brokken <email address hidden>  Mon, 27 May 2013 17:23:09 +0200

Upload details

Uploaded by:
Frank B. Brokken
Uploaded to:
Sid
Original maintainer:
Frank B. Brokken
Architectures:
any all
Section:
devel
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
bisonc++_4.04.01-1.dsc 2.1 KiB 151e95e6bb8ead53d731d0c0f03bbfc64ec8a95c2d35bc4359c5c9ca4be3559d
bisonc++_4.04.01.orig.tar.gz 649.5 KiB 84c9c4e35a7c774b6d5fa183f594a0c798579aa7eaede327b99523b851ec5c01
bisonc++_4.04.01-1.debian.tar.gz 11.7 KiB e4844925b64f5ca021ca880465ef17ff8ce56236a47a14aa0977c3d45f171e51

Available diffs

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++-doc: 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.
 .
 This package provides the supplemental documentation for Bisonc++.