From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_05,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11390f,4c42ac518eba0bbe X-Google-Attributes: gid11390f,public X-Google-Thread: 103376,4c42ac518eba0bbe X-Google-Attributes: gid103376,public X-Google-Thread: 1014db,4c42ac518eba0bbe X-Google-Attributes: gid1014db,public X-Google-Thread: 109fba,4c42ac518eba0bbe X-Google-Attributes: gid109fba,public From: bosworth@waterw.com (James L. Ryan) Subject: Re: Programming language vote - results Date: 1997/10/28 Message-ID: #1/1 X-Deja-AN: 286348225 References: <343fbb5a.0@news.iprolink.ch> <344BCED0.2D51@dynamite.com.au> <344F0863.41C6@lmco.com> <3451AA9D.259C@dynamite.com.au> <62te54$p4l$1@latte.cafe.net> <3454CEB7.7D3A42B8@acm.org> <01bce3bb$5d33da00$25a43a91@basil.omroep.nl> <34565F22.5B66C13E@acm.org> Organization: Taliesin Newsgroups: comp.lang.ada,comp.lang.apl,comp.lang.c,comp.lang.c++ Date: 1997-10-28T00:00:00+00:00 List-Id: In article <34565F22.5B66C13E@acm.org>, Robert Bernecky wrote: [snip] > > I am talking about history and what DID happen. There was no serious > attempt by any vendor to make APL fit into the ascii terminal world. > There is NO doubt in my mind that this seriously hampered APL's acceptance > as a popular language in the 70's and 80's. In the early seventies Burroughs APL had a "keyword" mode which was intended to make APL somewhat accessible from an ASCII terminal. When keywords were enabled APL letters mapped into ASCII lowercase and APL underscored letters mapped into ASCII uppercase. APL's special characters were represented by mnemonics embraced by less-than and greater-than symbols. Admittedly this was not intended to be a substitute for an APL terminal, but was intended to allow "emergency" access to APL from a non-APL terminal. With keywords on, and from an ASCII terminal, a line of APL might have looked as follows: average(+/data)
data Burroughs also contracted, in the early seventies, with Memorex to build a small number of terminals with 188 printing glyphs, 94 for ASCII and 94 for APL. These terminals could be either hard switched or soft switched between the character sets. The encodation of the characters was based upon the so-called APL/ASCII Typewriter Pairing overlay standard which was agreed upon at the Atlanta APL conference. The inclusion of the dual character set slowed the performance by a factor of two, but these terminals were still faster than the then only alternative, the 2741 and friends "golf-ball" terminals. Even though Burroughs attempted to sell these Memorex dual character set terminals, the market didn't seem interested. [snip] > > Not so. See above. It affects users and system administrators. Ever triedto > explain to someone back in the dark ages why your APL system couldn't print > a report with someone's name in Upper Case and Lower Case because APL > only had upper case and underbarred characters? Actually the ability to have computer output with both upper and lower case didn't come about until the early sixties. The computers I programmed in the late fifties used six bits instead of eight bits to represent characters. Rather amusingly, the first computer I programmed had 32 bit words which hosted five six-bit characters per word. You had the uppercase alphabet, the numerals, and a variety of punctuation characters. [snip] > -- James L. Ryan -- bosworth@waterw.com