Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!snorkelwacker!apple!oliveb!orc!mipos3!iwarp.intel.com!news
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: sort: thanks
Keywords: sort
Message-ID: <1990Feb1.223637.12939@iwarp.intel.com>
Date: 1 Feb 90 22:36:37 GMT
References: <1990Feb1.050145.21183@athena.mit.edu> <1990Feb1.163539.10576@iwarp.intel.com> <1990Feb1.193401.2229@athena.mit.edu>
Sender: news@iwarp.intel.com
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Distribution: usa
Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA
Lines: 20
In-Reply-To: ccount@athena.mit.edu (Craig A Counterman)

In article <1990Feb1.193401.2229@athena.mit.edu>, ccount@athena (Craig A Counterman) writes:
| Ah ha.  I hadn't thought of using the sort SUBROUTINE parameter in
| that manner.  It's less than intuitive for me.  This technique should
| go in the book, and some program in 'eg/' I think.

Believe me, it's less than intuitive for me too.  But, after reading
zillions of lines of code in, well, must be over 30 or 40 production
languages by now, some of the idioms become rather universal for doing
things like sorting and searching.  Perl lends itself to rather direct
expression of those as well as any Algol-derived language.  (Remember,
it all started with Algol... :-).

It will obviously go in the book.  I save *everything*.

Just another Perl hacker,
-- 
/=Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ==========\
| on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III      |
| merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn |
\=Cute Quote: "Welcome to Portland, Oregon, home of the California Raisins!"=/