flexc++ 2.03.00-1build1 source package in Ubuntu

Changelog

flexc++ (2.03.00-1build1) xenial; urgency=medium

  * Rebuild for bobcat 3 -> 4 ABI transition

 -- Michael Hudson-Doyle <email address hidden>  Tue, 01 Dec 2015 11:23:23 +1300

Upload details

Uploaded by:
Michael Hudson-Doyle
Sponsored by:
Matthias Klose
Uploaded to:
Xenial
Original maintainer:
Frank B. Brokken
Architectures:
any
Section:
devel
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
flexc++_2.03.00.orig.tar.gz 4.2 MiB 1c2572e0887cbaa623e1ab49c985341b23f24fd883a5a894ecd66d66d19b1af0
flexc++_2.03.00-1build1.debian.tar.xz 5.5 KiB 4504de13ce3529e575395b30271e02f992eede680c65adeabadb8a38f46413e0
flexc++_2.03.00-1build1.dsc 2.0 KiB 8ae3ee4ebee7756b98c1ac929d340ef6f6a1cb41ee1b351935497d72775d8224

View changes file

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.

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

 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.