summaryrefslogtreecommitdiff
path: root/pkgtools
diff options
context:
space:
mode:
authorrillig <rillig@pkgsrc.org>2006-02-28 23:32:47 +0000
committerrillig <rillig@pkgsrc.org>2006-02-28 23:32:47 +0000
commit6bd06c9cd1a1fe59f8288b845e2876bea7c32a03 (patch)
treec2e82407c5a27f3ca44e88788484e065d52cd9fa /pkgtools
parent582603326f6a7cf9a85f39f8db3f5c52b18c35ff (diff)
downloadpkgsrc-6bd06c9cd1a1fe59f8288b845e2876bea7c32a03.tar.gz
The rant on Perl has moved to the pkglint book.
Diffstat (limited to 'pkgtools')
-rw-r--r--pkgtools/pkglint/README12
1 files changed, 1 insertions, 11 deletions
diff --git a/pkgtools/pkglint/README b/pkgtools/pkglint/README
index 654863e3ab4..f6d94fa4fef 100644
--- a/pkgtools/pkglint/README
+++ b/pkgtools/pkglint/README
@@ -1,4 +1,4 @@
-$NetBSD: README,v 1.3 2006/02/28 15:21:09 rillig Exp $
+$NetBSD: README,v 1.4 2006/02/28 23:32:47 rillig Exp $
== Current problems ==
@@ -20,14 +20,4 @@ because most of pkgsrc is heavily based on preprocessors:
All this makes enhancing pkglint non-trivial. If you know of any
academic papers that might be of help in this case, please tell me.
-Additionally, the Perl programming language is not well suited to this
-kind of tool. It does not provide:
-
-- Sufficient static checking (especially for names of methods)
-- A type system (you can apply almost any operator to any kind of data)
-- Object orientation (needed for the future advanced parsers)
-- Narrow scope for constants (it's just ugly)
-- Enumeration data types
-- Structured data types
-
The pkglint source code is much too big for a single file.