[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#665783: O: bnfc -- Compiler front-end generator based on Labelled BNF



Control: retitle -1 O: bnfc -- Compiler front-end generator based on Labelled BNF
Control: affects -1 bnfc

With the upstream release of version 2.5.0, bnfc now ships a library in
addition to the binary.  This increases the packaging complexity enough that I
am not comfortable continuing as maintainer.  If someone wants to take over,
the package should probably be maintained within the Debian Haskell Group.

On Mon, Mar 26, 2012 at 07:14:01AM +0300, Antti-Juhani Kaijanaho wrote:
> Package: wnpp
> Severity: normal
> 
> I request an adopter for the bnfc package.
> 
> The package description is:
>  The BNF Converter is a compiler construction tool that generates a
>  compiler front-end and a readable syntax description document from a
>  Labelled BNF grammar. It was originally written to generate Haskell,
>  but it can now also be used for generating Java, C++, and C.
>  .
>  To process Haskell output, you need the Glorious Glasgow Haskell
>  Compiler (virtual package ghc), the Happy parser generator (package
>  happy) and the Alex scanner generator (package alex).
>  .
>  To process Java output, you need a Java compiler and virtual machine,
>  the CUP parser generator (package cup) and the JLex scanner generator
>  (package jlex).
>  .
>  To process C or C++ output, you need a C or C++ compiler,
>  respectively, the Bison parser generator (package bison) and the flex
>  scanner generator (package flex).
>  .
>  To process the generated documents, you need LaTeX (packages
>  tetex-base, tetex-bin, etc.).
> 
> 

-- 
Antti-Juhani Kaijanaho

Attachment: signature.asc
Description: Digital signature


Reply to: