The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Slashes (was: MS-DOS)
Date: Fri, 8 Jul 2016 10:52:19 -0400	[thread overview]
Message-ID: <CAC20D2NBP_SsjYRspmv8zwmFxg__w2mCrJOG0OBsB+u6M+GUPQ@mail.gmail.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3402 bytes --]

On Fri, Jul 8, 2016 at 7:09 AM, Steffen Nurpmeso <steffen at sdaoden.eu> wrote:

> ...and that actually makes me wonder why the engineers that
> created what became POSIX preferred slash instead
>
​I can not speak for anyone else.   But at the time when I was a part of
the /usr/group UNIX standards** mtgs  I personally do not believe I had
ever heard of the term "​solidus." Such a term maybe had been used in my
first form Latin classes from the 1960s, but by the 1980s  I had long ago
forgotten any/all of my Latin.  I certainly did not try to remember it as a
computer professional.

In those days many of us, including me, did (and still do) refer to the
asterisk as "splat" and the exclamation point as "bang"  from the sound
made by them when they printed yellow oiled paper @ 10 cps from the console
TTY.  But slash was what we called the character that is now next to the
shift key on modern keyboards.   I do not remember ever using, much less
needed to refer to, the character "back slash" until the unfortunate crap
that the folks in Redmond forced on the industry.   Although interestingly
enough, the vertical bar or UNIX "pipe" symbol was used and discussed
freely in those days.   I find it interesting that Redmond-ism became the
unshifted character, not the vertical bar by the shear force of economics
of the PC.

Clem

** For those that do not know (my apologies to those that do) the 1985
/usr/group standards committee was the forerunner to IEEE P1003.  Which we
published as the first "official UNIX API standard agreed by the community"
(I still have a hardcopy).  But neither /usr/group nor USENIX had the
political authority to bring an official standard to FIPS, ANSI, ECMA, ISO
or like, while IEEE did.  So a few months before the last meeting, Jim
Issak petitioned IEEE for standards status, and the last meeting of the
/usr/group UNIX standards meeting was very short -- about 10 minutes.   We
voted to disband and then everyone in the room officially reformed a few
minutes later all signing in as IEEE P1003, later to be called POSIX.  For
further historical note, I was a "founding member" of both groups and the
editor of a number of early drafts (numbers 5-11 IIRC), as well as the
primary author of the Tape Format and Terminal I/O sections of P1003.1.
With Keith Bostic, I would later be part of the P1003.2 and pen the
original PAX compromise.  After that whole mess I was so disgusted with the
politics of the effort, I stopping going to the POSIX mtgs.

PPS While I did not work for them at the time, you can blame DEC for the
mess with the case/character sets in the POSIX & FIPS standards.   A number
of the compromises in the standard documents were forced by VMS, 7-bit
(case insensitivity) being the prime one.   While we did get in the
rational section of document that it was suggested/advised that systems
implementations and applications code be case insensitive and 8 bit clean
so that other character sets could be supported.  However the DEC folks
were firmly against anything more than 7-bit ASCII and supporting anything
in that character set. My memory is that the IBM folks were silent at the
time and just let the DEC guys carry the torch for 1960's 7-bit US English.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160708/fdf012d6/attachment-0001.html>


             reply	other threads:[~2016-07-08 14:52 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 14:52 Clem Cole [this message]
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-10 14:38       ` [TUHS] Slashes Christian Neukirchen
  -- strict thread matches above, loose matches on Subject: below --
2016-07-10  1:41 [TUHS] Slashes (was: MS-DOS) 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
2016-07-13 10:09         ` Joerg Schilling
2016-07-10 21:10 ` Sven Mascheck
2016-07-08 17:36 Norman Wilson
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=CAC20D2NBP_SsjYRspmv8zwmFxg__w2mCrJOG0OBsB+u6M+GUPQ@mail.gmail.com \
    --to=clemc@ccc.com \
    /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).