From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] Slashes (was: MS-DOS)
Date: Wed, 13 Jul 2016 21:24:54 +1200 (NZST) [thread overview]
Message-ID: <1468401894.578608e6809bb@www.paradise.net.nz> (raw)
In-Reply-To: <3A3AEFA5-8B6B-472D-85F1-1636646418D9@ronnatalie.com>
IIRC, Steven Kaisler's book "The Design of Operating Systems for Small Computer
Systems" used the up-arrow as the pseudocode's pointer symbol. Did Pascal do
that as well, or was that only on some of the Pascal dialects?
Wesley Parish
Quoting Ronald Natalie <ron at ronnatalie.com>:
> We had teletypes that went both ways. Some had the arrows and some had
> the caret/underscore.
>
> > On Jul 12, 2016, at 1:53 PM, Tim Bradshaw <tfb at tfeb.org> wrote:
> >
> > On 10 Jul 2016, at 02:46, Steve Nickolas <usotsuki at buric.co> wrote:
> >
> >> Some 8-bit computers used up arrow for ^ even into the 80s, I think
> Radio Shack's did at least.
> >
> > I'm fairly (but not completely) sure that the Xerox Lisp machines had
> caret as up arrow, and they certainly had left arrow for underscore.
> They persisted into the late 80s when I used them. I'm not sure what
> appeared on the keyboards, which may have been more modern than the
> character set used by the system, since the same hardware was sold with
> different software on it.
>
>
"I have supposed that he who buys a Method means to learn it." - Ferdinand Sor,
Method for Guitar
"A verbal contract isn't worth the paper it's written on." -- Samuel Goldwyn
next prev parent reply other threads:[~2016-07-13 9:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 1:41 Norman Wilson
2016-07-10 1:46 ` Steve Nickolas
2016-07-10 1:52 ` John Cowan
2016-07-12 17:53 ` Tim Bradshaw
2016-07-12 18:05 ` Ronald Natalie
2016-07-13 9:24 ` Wesley Parish [this message]
2016-07-13 10:09 ` Joerg Schilling
2016-07-10 21:10 ` Sven Mascheck
-- strict thread matches above, loose matches on Subject: below --
2016-07-08 17:36 Norman Wilson
2016-07-08 14:52 Clem Cole
2016-07-08 14:59 ` Clem Cole
2016-07-08 15:47 ` Nemo
2016-07-08 16:31 ` Steffen Nurpmeso
2016-07-08 20:29 ` Clem Cole
2016-07-08 16:27 ` Steffen Nurpmeso
2016-07-08 18:00 ` Steve Nickolas
2016-07-08 18:23 ` Random832
2016-07-08 20:49 ` Clem Cole
2016-07-08 21:09 ` Ron Natalie
2016-07-08 21:16 ` John Cowan
2016-07-08 21:45 ` Ron Natalie
2016-07-09 16:47 ` Dave Horsfall
2016-07-09 17:03 ` John Cowan
2016-07-09 17:21 ` Milo Velimirovic
2016-07-08 11:25 Norman Wilson
2016-07-08 13:16 ` John Cowan
2016-07-08 14:06 ` Brantley Coile
2016-07-02 0:12 [TUHS] MS-DOS Norman Wilson
2016-07-02 1:13 ` Steve Nickolas
2016-07-07 5:02 ` [TUHS] Slashes (was: MS-DOS) Greg 'groggy' Lehey
2016-07-07 13:43 ` Nemo
2016-07-07 14:11 ` John Cowan
2016-07-07 14:18 ` Steffen Nurpmeso
2016-07-07 23:47 ` Greg 'groggy' Lehey
2016-07-08 5:40 ` scj
2016-07-08 7:06 ` Greg 'groggy' Lehey
2016-07-08 11:09 ` Steffen Nurpmeso
2016-07-09 0:03 ` Greg 'groggy' Lehey
2016-07-09 14:24 ` Steffen Nurpmeso
2016-07-09 16:38 ` John Cowan
2016-07-11 11:20 ` Tony Finch
2016-07-11 11:54 ` Nemo
2016-07-11 13:15 ` Joerg Schilling
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=1468401894.578608e6809bb@www.paradise.net.nz \
--to=wes.parish@paradise.net.nz \
/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).