1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
Source: bisonc++
Section: devel
Priority: optional
Maintainer: Frank B. Brokken <f.b.brokken@rug.nl>
Uploaders: tony mancill <tmancill@debian.org>
Build-Depends: debhelper-compat (= 13),
flexc++ (>= 2.08.01),
libbobcat-dev (>= 6.02.02),
icmake (>= 13.00.03),
yodl (>= 4.02.02)
Standards-Version: 4.7.2
Homepage: https://fbb-git.gitlab.io/bisoncpp/
Vcs-Browser: https://salsa.debian.org/debian/bisoncpp
Vcs-Git: https://salsa.debian.org/debian/bisoncpp.git
Rules-Requires-Root: no
Package: bisonc++
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Suggests: bisonc++-doc, flexc++
Description: 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.
Package: bisonc++-doc
Architecture: all
Multi-Arch: foreign
Section: doc
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: 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++.
|
