Source: pgpg
Section: golang
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Uploaders: Stephen Kitt <skitt@debian.org>,
Build-Depends: debhelper (>= 13.26~),
               dh-sequence-golang,
               golang-any,
               golang-github-davecgh-go-spew-dev,
               golang-github-pmezard-go-difflib-dev,
               golang-github-stretchr-testify-dev,
               golang-gopkg-yaml.v3-dev,
Testsuite: autopkgtest-pkg-go
Standards-Version: 4.7.4
Vcs-Browser: https://salsa.debian.org/go-team/packages/pgpg
Vcs-Git: https://salsa.debian.org/go-team/packages/pgpg.git
Homepage: https://github.com/johnkerl/pgpg
XS-Go-Import-Path: github.com/johnkerl/pgpg
X-DH-Compat: 14

Package: pgpg
Section: devel
Architecture: any
Description: Parser generator and parsing library (program)
 PGPG is the Pretty Good Parser Generator. Its goals are as follows:
 .
  * Implement a few basic algorithms.
  * Reuse code whenever possible, across multiple algorithms like
    LALR/LR.
  * Make good use of classes---e.g. lexer.match() rather than global
    match() which are commonly used in intro-to-parsing textbooks.
  * Be lucid above all else. Lexing/parsing is ubiquitous in the
    modern world, and forms a large part of our world. Yet sadly such
    tools are too often arcane and confusing. PGPG is transparent,
    inclusive, and explains itself openly.
  * Offer choices:
    - Sometimes a parser-generator is overkill---for simpler grammars,
      a hand-written lexer and a hand-written recursive-descent parser
      are quite satisfactory. PGPG offers reusable, easy-to-understand
      examples here.
    - Sometimes a hand-written lexer/parser is underkill---yet parser-
      generators can be complex and intimidating. Here, too, PGPG
      offers reusable, easy-to-understand examples.
    - PGPG offers classes that reduce code-duplication for various
      lex/parse implementations: you can reuse what you want, and
      hand-write what you want.
    - PGPG offers grammar-to-parser all in one process invocation, or
      parser-generate to language-independent storage (probably JSON),
      or traditional parser-generate directly to
      implementation-language code.
 .
 This package contains the parser generators and associated tools.

Package: golang-github-johnkerl-pgpg-dev
Architecture: all
Multi-Arch: foreign
Description: Parser generator and parsing library (library)
 PGPG is the Pretty Good Parser Generator. Its goals are as follows:
 .
  * Implement a few basic algorithms.
  * Reuse code whenever possible, across multiple algorithms like
    LALR/LR.
  * Make good use of classes---e.g. lexer.match() rather than global
    match() which are commonly used in intro-to-parsing textbooks.
  * Be lucid above all else. Lexing/parsing is ubiquitous in the
    modern world, and forms a large part of our world. Yet sadly such
    tools are too often arcane and confusing. PGPG is transparent,
    inclusive, and explains itself openly.
  * Offer choices:
    - Sometimes a parser-generator is overkill---for simpler grammars,
      a hand-written lexer and a hand-written recursive-descent parser
      are quite satisfactory. PGPG offers reusable, easy-to-understand
      examples here.
    - Sometimes a hand-written lexer/parser is underkill---yet parser-
      generators can be complex and intimidating. Here, too, PGPG
      offers reusable, easy-to-understand examples.
    - PGPG offers classes that reduce code-duplication for various
      lex/parse implementations: you can reuse what you want, and
      hand-write what you want.
    - PGPG offers grammar-to-parser all in one process invocation, or
      parser-generate to language-independent storage (probably JSON),
      or traditional parser-generate directly to
      implementation-language code.
 .
 This package contains the parsing library.
