[pkgsrc/trunk]: pkgsrc/devel/py-TPG Initial import of py-TPG 2.1.6

[recht <recht%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/e2a4093de633
branches:  trunk
changeset: 461406:e2a4093de633
user:      recht <recht%pkgsrc.org@localhost>
date:      Mon Sep 15 22:08:35 2003 +0000

description:
Initial import of py-TPG 2.1.6
based upon the pkg provided by Michal Pasternak in PR 21982

TPG can very simply write parsers that are usefull for most every day needs
(even if it can't make your coffee). With a very clear and simple syntax,
you can write an attributed grammar that is translated into a recursive
descendant parser. TPG generated code is very closed to the original
grammar. This means that the parser works "like" the grammar. A grammar rule
can be seen as a method of the parser class, symbols as method calls,
attributes as method parameters and semantic values as return values. You
can also add Python code directly into grammar rules and build abstract
syntax trees while parsing.

diffstat:

 devel/py-TPG/DESCR    |  13 +++++++++++++
 devel/py-TPG/Makefile |  16 ++++++++++++++++
 devel/py-TPG/PLIST    |  18 ++++++++++++++++++
 devel/py-TPG/distinfo |   4 ++++
 4 files changed, 51 insertions(+), 0 deletions(-)

diffs (67 lines):

diff -r 7d5511f90c56 -r e2a4093de633 devel/py-TPG/DESCR
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/py-TPG/DESCR        Mon Sep 15 22:08:35 2003 +0000
@@ -0,0 +1,13 @@
+TPG can very simply write parsers that are usefull for most every day needs
+(even if it can't make your coffee). With a very clear and simple syntax,
+you can write an attributed grammar that is translated into a recursive
+descendant parser. TPG generated code is very closed to the original
+grammar. This means that the parser works "like" the grammar. A grammar rule
+can be seen as a method of the parser class, symbols as method calls,
+attributes as method parameters and semantic values as return values. You
+can also add Python code directly into grammar rules and build abstract
+syntax trees while parsing.
+
+The first application of TPG is TPG itself. The first (not released) version
+of TPG has been written by hand then was used to generate next versions. Now
+TPG can generate itself. 
diff -r 7d5511f90c56 -r e2a4093de633 devel/py-TPG/Makefile
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/py-TPG/Makefile     Mon Sep 15 22:08:35 2003 +0000
@@ -0,0 +1,16 @@
+# $NetBSD: Makefile,v 1.1.1.1 2003/09/15 22:08:35 recht Exp $
+#
+
+DISTNAME=              TPG-2.1.6
+CATEGORIES=            devel
+MASTER_SITES=          http://christophe.delord.free.fr/soft/tpg/
+
+MAINTAINER=            dotz%irc.pl@localhost
+HOMEPAGE=              http://christophe.delord.free.fr/soft/tpg/
+COMMENT=               ToyParserGenerator for Python
+
+PYTHON_VERSIONS_ACCEPTED=      23 23pth 22 22pth
+PYDISTUTILSPKG=        # defined
+
+.include "../../lang/python/extension.mk"
+.include "../../mk/bsd.pkg.mk"
diff -r 7d5511f90c56 -r e2a4093de633 devel/py-TPG/PLIST
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/py-TPG/PLIST        Mon Sep 15 22:08:35 2003 +0000
@@ -0,0 +1,18 @@
+@comment $NetBSD: PLIST,v 1.1.1.1 2003/09/15 22:08:35 recht Exp $
+bin/tpg
+${PYSITELIB}/tpg/Release.py
+${PYSITELIB}/tpg/Release.pyc
+${PYSITELIB}/tpg/Release.pyo
+${PYSITELIB}/tpg/__init__.py
+${PYSITELIB}/tpg/__init__.pyc
+${PYSITELIB}/tpg/__init__.pyo
+${PYSITELIB}/tpg/base.py
+${PYSITELIB}/tpg/base.pyc
+${PYSITELIB}/tpg/base.pyo
+${PYSITELIB}/tpg/codegen.py
+${PYSITELIB}/tpg/codegen.pyc
+${PYSITELIB}/tpg/codegen.pyo
+${PYSITELIB}/tpg/parser.py
+${PYSITELIB}/tpg/parser.pyc
+${PYSITELIB}/tpg/parser.pyo
+@dirrm ${PYSITELIB}/tpg
diff -r 7d5511f90c56 -r e2a4093de633 devel/py-TPG/distinfo
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/py-TPG/distinfo     Mon Sep 15 22:08:35 2003 +0000
@@ -0,0 +1,4 @@
+$NetBSD: distinfo,v 1.1.1.1 2003/09/15 22:08:35 recht Exp $
+
+SHA1 (TPG-2.1.6.tar.gz) = b8ccbefd41b16514a2ad2a86b97dc9ab6cc3828e
+Size (TPG-2.1.6.tar.gz) = 417009 bytes