[pkgsrc/trunk]: pkgsrc/pkgtools/pkglint The rant on Perl has moved to the pkg...

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/a55e6079f321
branches:  trunk
changeset: 508950:a55e6079f321
user:      rillig <rillig%pkgsrc.org@localhost>
date:      Tue Feb 28 23:32:47 2006 +0000

description:
The rant on Perl has moved to the pkglint book.

diffstat:

 pkgtools/pkglint/README |  12 +-----------
 1 files changed, 1 insertions(+), 11 deletions(-)

diffs (24 lines):

diff -r 06338e0c0929 -r a55e6079f321 pkgtools/pkglint/README
--- a/pkgtools/pkglint/README   Tue Feb 28 23:25:23 2006 +0000
+++ b/pkgtools/pkglint/README   Tue Feb 28 23:32:47 2006 +0000
@@ -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 @@
 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.