bisonc++ 4.10.01-1build2 source package in Ubuntu

Changelog

bisonc++ (4.10.01-1build2) wily; urgency=medium

  * No-change rebuild against libbobcat3v5

 -- Martin Pitt <email address hidden>  Thu, 13 Aug 2015 07:42:38 +0200

Upload details

Uploaded by:
Martin Pitt
Uploaded to:
Wily
Original maintainer:
Ubuntu Developers
Architectures:
any all
Section:
devel
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
bisonc++_4.10.01.orig.tar.gz 637.3 KiB d03b1c3982f7cff9663382cb6933ccc5aa8ce35a7ccbd6f76769aa261777bf0b
bisonc++_4.10.01-1build2.debian.tar.xz 11.8 KiB 96a8b42b9f0042b411fa58dac11327030d98e27e6065591ee169c6020c89bcf4
bisonc++_4.10.01-1build2.dsc 2.1 KiB 3f5e9ed9bff43912ae66f83339898d7cb82e6eb38afc1e353fd7bb013d32ca0e

View changes file

Binary packages built by this source

bisonc++: No summary available for bisonc++ in ubuntu wily.

No description available for bisonc++ in ubuntu wily.

bisonc++-dbgsym: debug symbols for package bisonc++

 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: No summary available for bisonc++-doc in ubuntu wily.

No description available for bisonc++-doc in ubuntu wily.