Article View: comp.unix.shell
Article #4634Re: Gawk v24.7: Why Bother???
From: john John R MacMillan
Date: Fri, 21 Apr 1995 00:00
Date: Fri, 21 Apr 1995 00:00
18 lines
1523 bytes
1523 bytes
|the current FUTURES file, I simply couldn't believe it. It read just like |a treatise on how to recreate Perl! Doesn't anyone out there realize that |we've already done all this stuff -- most of it many years ago??? Well, I can't claim to speak for all gawk users, but for me the real advantage is that I can get useful new features _in a language I already know_. I realize that Perl can do everything I need to, but I don't know Perl, and I do know awk, and it's much easier to make use of a new feature or two than learn a whole new language. Yes, Perl did most of these things years ago, and did so because they were useful features. Why shouldn't gawk benefit from them as well? Why did Perl add object-oriented features? Smalltalk has had them for AGES, didn't Larry know he was just reinventing the wheel? (Rhetorical question alert.) As for sticking with a single language spec (eg. POSIX awk), don't you believe languages should evolve? Perl certainly has.
Technical Details
Message-ID:
<D7EnF5.ILw@sco.COM>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<3mpj9f$d1h@csnews.cs.colorado.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1025b4,4df32fd703a6b724 X-Google-Attributes: gid1025b4,public X-Google-Thread: 1012a6,4df32fd703a6b724 X-Google-Attributes: gid1012a6,public From: john@sco.COM. (John R MacMillan) Subject: Re: Gawk v24.7: Why Bother??? Date: 1995/04/21 Message-ID: <D7EnF5.ILw@sco.COM> X-Deja-AN: 101361843 sender: news@sco.COM (News administration) references: <3mpj9f$d1h@csnews.cs.colorado.edu> organization: SCO Canada, Inc. newsgroups: comp.unix.shell,gnu.misc.discuss