From: "AMSRL-CI-CN" <gwyn@arl.army.mil>
To: 9fans@cse.psu.edu
Subject: Re: Fwd: Re: [9fans] samuel (fwd)
Date: Mon, 4 Mar 2002 10:04:01 +0000 [thread overview]
Message-ID: <GsB9uz.Grn@arl.army.mil> (raw)
In-Reply-To: <3cb3dded4b8cad85cd6887800a46bc25@plan9.bell-labs.com>
"rob pike" <rob@plan9.bell-labs.com> wrote in message
news:3cb3dded4b8cad85cd6887800a46bc25@plan9.bell-labs.com...
> This all drives home my position on these matters, which is that
> general purpose tools that work well together almost always trump
> special purpose tools such as language-specific ones. And even when
> they don't, they win overall by being applicable to domains far beyond
> the reach of the special-purpose ones.
Indeed! I think the main reason Unix was such a hit was that it
provided a relatively complete and well integrated text-file tool kit
along with means to conveniently combine the tools.
Many years back I posted to sci.crypt an example of the use of
those tools in (intermediate level) cryptanalysis. I can't seem to
find it via DejaNews, though. I did find a posting where I gave
examples of how one's own small custom programs can be
effectively combined with the standard toolkit
(typo corrected in this reprint):
$ # Find anagram of NABAAN:
$ anabet < /usr/pub/words > analist
$ echo NABAAN | anabet # also illustrates what anabet does
AAABNN NABAAN
$ grep '^AAABNN ' < analist
AAABNN BANANA
$ # Find keyword corresponding to transposition key 3 1 8 2 7 6 5 4:
$ transkey < /usr/pub/words > keylist
$ grep '^3 1 8 2 7 6 5 4:' < keylist
3 1 8 2 7 6 5 4: CARBOLIC
next prev parent reply other threads:[~2002-03-04 10:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 16:15 rob pike
2002-03-04 10:04 ` AMSRL-CI-CN [this message]
2002-03-05 9:40 ` ozan s yigit
2002-03-06 9:51 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2002-03-04 15:24 Bengt Kleberg
2002-03-05 9:41 ` Douglas A. Gwyn
2002-03-05 10:04 ` George Michaelson
2002-03-06 9:51 ` Thomas Bushnell, BSG
2002-03-06 15:56 ` ozan s yigit
2002-03-07 9:56 ` Thomas Bushnell, BSG
2002-03-07 16:46 ` ozan s yigit
2002-03-07 17:55 ` Thomas Bushnell, BSG
2002-03-08 9:59 ` ozan s. yigit
2002-03-06 19:39 ` Andrew Simmons
2002-03-05 10:18 ` Boyd Roberts
2002-03-04 14:41 Russ Cox
2002-03-04 11:43 Bengt Kleberg
2002-03-04 14:02 ` Howard Trickey
2002-03-05 9:41 ` Douglas A. Gwyn
2002-03-05 10:42 ` Boyd Roberts
2002-03-04 0:21 Andrew Simmons
2002-03-05 9:34 ` Boyd Roberts
2002-03-01 17:58 Russ Cox
2002-03-05 9:22 ` Boyd Roberts
2002-03-01 17:29 anothy
2002-03-01 17:13 Bengt Kleberg
2002-03-01 16:04 Russ Cox
2002-02-02 17:05 ` Matt H
2002-03-01 17:12 ` Boyd Roberts
2002-03-04 10:04 ` David Rubin
[not found] <rob@plan9.bell-labs.com>
2002-03-01 6:20 ` rob pike
2002-03-01 6:34 ` George Michaelson
2002-03-01 12:04 ` Boyd Roberts
2002-03-01 2:51 Sam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=GsB9uz.Grn@arl.army.mil \
--to=gwyn@arl.army.mil \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).