summaryrefslogtreecommitdiff
path: root/devel/py-TPG/PLIST
diff options
context:
space:
mode:
authorrecht <recht@pkgsrc.org>2003-09-15 22:08:35 +0000
committerrecht <recht@pkgsrc.org>2003-09-15 22:08:35 +0000
commitb936903f95a0d89753ec6c1216ab93b97a64265d (patch)
tree4bdf09f3e5dfa8976bc1c4c4e1c4f2b3877ce449 /devel/py-TPG/PLIST
parent41614a9ed1c71d1084507af8e0de4ef768ce155b (diff)
downloadpkgsrc-b936903f95a0d89753ec6c1216ab93b97a64265d.tar.gz
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 (limited to 'devel/py-TPG/PLIST')
-rw-r--r--devel/py-TPG/PLIST18
1 files changed, 18 insertions, 0 deletions
diff --git a/devel/py-TPG/PLIST b/devel/py-TPG/PLIST
new file mode 100644
index 00000000000..2c3f70aa835
--- /dev/null
+++ b/devel/py-TPG/PLIST
@@ -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