bisonc++ 2.09.03-1 source package in Ubuntu

Changelog

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

  [ Frank B. Brokken ]
  * new upstream release cleans code and recognizes CXXFLAGS and LDFLAGS
  * Build-Depends on g++ (>= 4:4.6.0)

  [ tony mancill ]
  * Add build-arch target to debian/rules.
 -- Ubuntu Archive Auto-Sync <email address hidden>   Wed,  29 Jun 2011 08:25:24 +0000

Upload details

Uploaded by:
Ubuntu Archive Auto-Sync
Uploaded to:
Oneiric
Original maintainer:
Frank B. Brokken
Architectures:
any
Section:
devel
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Precise release universe devel

Downloads

File Size SHA-256 Checksum
bisonc++_2.09.03.orig.tar.gz 613.9 KiB f0d303085ddbc1948002950fa5d9c017fe81a0c4e77376ecd06446b7005edd9a
bisonc++_2.09.03-1.debian.tar.gz 11.3 KiB 5f4c01fd4af8e709f2d4381ecad6ec7246eb13c4c031557d6821b293f836d42c
bisonc++_2.09.03-1.dsc 1.9 KiB 3ac20c76158e9efb1411979b4791a0c6d622b7efe07d80d729231feb12d7efa0

Available diffs

View changes file

Binary packages built by this source

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

No description available for bisonc++ in ubuntu quantal.

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