Newsgroups: comp.lang.apl
Path: watmath!watserv2.uwaterloo.ca!mach1!torn!utnut!cs.utexas.edu!usc!howland.reston.ans.net!agate!headwall.Stanford.EDU!kithrup.com!canuck.cygnus.com!dje
From: dje@canuck.cygnus.com (Doug Evans)
Subject: Re: A modest proposal
Organization: Kithrup Enterprises, Ltd.
References: <635727@MTS.cc.Wayne.edu>
Nntp-Posting-Host: canuck.cygnus.com
Message-ID: <C5uoK0.HAp@kithrup.com>
Sender: news@kithrup.com (Network News)
X-Newsreader: Tin 1.1 PL5
Date: Wed, 21 Apr 1993 20:21:21 GMT
Lines: 31

Robert_Brown@MTS.cc.Wayne.edu wrote:
>  
> In article <735171646.AA03641@blkcat.UUCP>,
> David.Michelson@f70.n109.z1.fidonet.org (David Michelson) writes:
>  > I have a modest proposal for ASCII transmission of APL code:
>    :
>    :
>  
> There have been MANY methods implemented for representing APL code on
> non-APL device.  Lee Dickey has a collection of 35+ of them.  Most, if
> not all, are parsable, since they were used in the implementation of
> one or more interpreters.
>  
> I don't like Davids appraoch, but his heart is in the right place!
>  
> What we need is not ANOTHER way to represent these, but AGREEMENT on
> which SINGLE ONE to use.  Perhaps someone should get this list from Lee,
> examine it, decide upon the best scheme, and post the results.  I'm sure
> that extensions would be required, but that would not be a major problem.
> The representation scheme could be standardized, and a pointer to it can
> be included in the FAQ.  People could write code to translate to/from
> this scheme, and we could then move code across the Net much more easily.

This is partly a test message, and partly a message to say I couldn't
agree more!

--
Doug Evans           Cygnus Support, Mountain View, CA
dje@cygnus.com                         +1 415 903 1400

----- A life lived in fear is a life half lived. -----
