Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!zds-ux!gerry
From: gerry@zds-ux.UUCP (Gerry Gleason)
Newsgroups: comp.arch
Subject: Re: In computing, late-bloomers are usually never-bloomers
Message-ID: <53@zds-ux.UUCP>
Date: 20 Dec 89 16:24:30 GMT
References: <24317@cup.portal.com> <480@dmk3b1.UUCP> <1989Nov28.104128.8045@hellgate.utah.edu> <1Tcfjq#9jMTbv=eric@snark.uu.net> <3511@convex.UUCP> <1933@eric.mpr.ca> <1TfOZ0#142gXX=eric@snark.uu.net> <629274691.11005@myrias.com>
Reply-To: gerry@zds-ux.UUCP (Gerry Gleason)
Organization: Zenith Data Systems
Lines: 14

In article <629274691.11005@myrias.com> cmt@myrias.com (Chris Thomson) writes:
>. . .  APL features keep popping up, for instance as vector-valued
>subscripts in F8X.

The best use I've seen for APL was in a book on ALU architecture.  They
used APL algorithms to describe hardware, with vector operations mapping
to arrays of hardware elements and control/data flow mapping to
interconnections.  The APL descriptions were at least as clear as block
diagrams would be.

Also, your comments on Algol (Algol60 is probably the right reference)
are right on.  It's the grandaddy of all block structured languages.

Gerry Gleason