# bnfc mit Homebrew, apt, pacman installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für bnfc in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:bnfc ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install bnfc ``` Evidenz: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install bnfc ``` Evidenz: Debian stable package indexes: bnfc from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - pacman (92%): ```sh sudo pacman -S bnfc ``` Evidenz: Arch Linux sync databases: bnfc from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## Paketfakten - **Paketschlüssel:** brew:bnfc - **Paketmanager:** Homebrew - **Version:** 2.9.6.3 - **Quellzusammenfassung:** BNF Converter - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-07-22T02:42:18Z - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - bnfc (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 2.9.6.3 ## Projektgeschichte und Nutzung BNFC, the BNF Converter, is a compiler-construction tool that turns a Labelled BNF grammar into a compiler front end: abstract syntax, lexer, parser, pretty-printer, test bench, and documentation. ### Projektgeschichte BNFC started at Chalmers and the University of Gothenburg. A 2004 Haskell workshop demonstration by Markus Forsberg and Aarne Ranta says Forsberg and Ranta began development in 2002 as a tool generating Haskell. The same source records that Michael Pellauer retargeted BNFC to C, C++, and Java in 2003, moving it from a Haskell-only generator toward a multilingual compiler-front-end generator. Modern BNFC documentation describes the LBNF formalism independently of any one output language, and the project now advertises generation for Haskell, Agda, C, C++, Java, OCaml, XML representations, and Pygments syntax highlighters. ### Adoptionsgeschichte BNFC found adoption in programming-languages courses, research prototypes, and small language implementations where the grammar is the most stable artifact and hand-written front ends would be repetitive. Its package-manager footprint is narrower than mainstream parser generators but meaningful: Homebrew, Debian/Ubuntu, Arch, and Haskell package ecosystems carry it for developers who want an executable generator rather than a library-only parser toolkit. ### Wie es verwendet wird A user writes an LBNF grammar, runs bnfc, and then compiles the generated lexer/parser and abstract-syntax code with the target language's usual parser tooling, such as Alex and Happy for Haskell or Flex/Bison-style tools for C-family output. BNFC is especially useful when the same grammar should produce both implementation artifacts and a readable language specification, keeping parser code, AST constructors, pretty printers, and documentation aligned. ### Warum Paket-Nerds sich dafür interessieren BNFC is package-nerd-significant because it packages an academic compiler-construction idea as a practical command-line generator. It is not just yacc with another syntax; its labeled grammar rules become typed abstract syntax across target languages. For language-tooling nerds, BNFC sits in the interesting space between parser generators, syntax-specification formalisms, and teaching tools. It makes a grammar file the source of truth for several generated artifacts that are otherwise easy to let drift. Its long survival in package managers matters because many compiler-course and research tools depend on old but useful grammar generators being installable without reconstructing a Chalmers-era toolchain by hand. ### Zeitleiste - 2002: Forsberg and Ranta start BNFC as a Haskell-generating tool. - 2003: BNFC is retargeted to C, C++, and Java by Michael Pellauer. - 2004: BNFC is demonstrated at the ACM SIGPLAN Haskell workshop. - 2010s: BNFC migrates into modern package managers and public GitHub maintenance. - 2020s: BNFC documentation lists target-language support including Haskell, Agda, C, C++, Java, and OCaml. ### Related projects - Alex and Happy: Haskell lexer and parser tools often used with BNFC's Haskell backend. - Flex and Bison: traditional lexer/parser tools related to BNFC's C/C++ style generated front ends. - ANTLR, yacc, and Menhir: parser-generator neighbors with different grammar models and target ecosystems. - LBNF: the Labelled BNF grammar formalism used by BNFC. ### Quellen - - - - - - - ## Sicherheitshinweise narrow executable package without higher-risk signals. - **Geiger-Risiko:** grün / niedrig - narrow executable package without higher-risk signals ## Andere Paketmanager-Einträge - Debian apt - bnfc - 2.9.5-1: normalized package name match | Debian stable package indexes: bnfc from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Compiler front-end generator based on Labelled BNF | https://bnfc.digitalgrammars.com/ - Ubuntu apt - bnfc - 2.9.5-1: normalized package name match | Ubuntu 24.04 LTS package indexes: bnfc from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Compiler front-end generator based on Labelled BNF | https://bnfc.digitalgrammars.com/ - pacman - bnfc - 2.9.6.3-35: normalized package name match | Arch Linux sync databases: bnfc from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A compiler front-end generator. | https://bnfc.digitalgrammars.com/ ## Combined YAML source View the package source record on GitHub. [combined/bnfc.yml](https://github.com/mxcl/pkgdb/blob/main/combined/bnfc.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph