Ubuntu
bisonc++ package

bisonc++ 6.09.00-1 source package in Ubuntu

Changelog

bisonc++ (6.09.00-1) unstable; urgency=medium

  [ Frank B. Brokken ]
  * New upstream version 6.09.00 ignores end-of-line comment used in
    %polymorphic %type specifications.
  * Updated package construction requirements: icmake >= 12.01.00

  [ tony mancill ]
  * Freshen years in debian/copyright
  * Bump Standards-Version to 4.7.0

 -- tony mancill <email address hidden>  Mon, 27 May 2024 15:47:23 -0700

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 Pocket Published Component Section
Oracular release universe devel

Downloads

File Size SHA-256 Checksum
bisonc++_6.09.00-1.dsc 2.0 KiB 32255be0ea598d4c646aa729bd7463f42c8d8ceeb822aa6118ee8e2f1777c406
bisonc++_6.09.00.orig.tar.gz 501.2 KiB 3dc511ce99e6acc2d24ea53b7fa9a361deac18a3189b4f5adc020406b65ee6b2
bisonc++_6.09.00-1.debian.tar.xz 13.6 KiB f8540156c83fc32da2be6ac0d0e99107ad685381284c606e22700f46d78944ee

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++-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++.