flexc++ 1.05.00-1 source package in Ubuntu

Changelog

flexc++ (1.05.00-1) unstable; urgency=low


  * New upstream release disallows path-specifications for destination
    filenames 

  * Removed git-build target from debian/rules

  * Removed explicit g++ compiler version specification (4.7) from
    debian/rules 

 -- Frank B. Brokken <email address hidden>  Tue, 28 May 2013 18:44:01 +0200

Upload details

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

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
flexc++_1.05.00-1.dsc 2.0 KiB e2c27385d6f2f927011159493380159d3c82349e8625f7260983a7f14826c540
flexc++_1.05.00.orig.tar.gz 3.6 MiB 2c88018cf3fabad3f52045bd3a070a8e321a36cb5d68cdaa756b920878e4f691
flexc++_1.05.00-1.debian.tar.gz 4.9 KiB f5203aaec68c231b91330196f037aa7260a9b414ec3fcab0e603ae3659f9bfc0

Available diffs

No changes file available.

Binary packages built by this source

flexc++: Flex-style scanner generator for C++

 Flexc++ was designed after `flex'. Flexc++ offers as compared to flex's C++
 option a cleaner class-design.
 .
 Flexc++ generates a scanner class that is ready for use, as well as a member
 function producing the lexical scanner tokens (lex()). The class can easily
 be provided with additional members without the need for polymorphic
 functions. Consequently, classes generated by flexc++ have no virtual members
 and actually have but one public member: lex(), replacing the old-style flex
 and flex++ yylex() function.
 .
 Flexc++ offers many options, among which an option to define classes
 generated by flexc++ in a separate namespace. This allows developers to
 define additional symbols, even outside of the class generated by flexc++,
 without encountering name-collision problems. With flexc++, artificial means
 to prevent name-collisions, like the yy-conventions used by flex and flex++
 are no longer required. Flexc++ generates C++ code. If C code is required,
 flex should be used. Flexc++'s grammar requirements are highly compatible
 with flex's requirements, so converting a flex grammar into a flexc++ grammar
 should be fairly simple.
 .
 In addition to the flexc++ scanner generator itself and several skeleton
 files, the package contains an extensive man-page, as well as a full manual
 rewritten after the original flex manual, and several examples.