The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] // comment in C++
Date: Thu, 9 Feb 2017 10:22:13 +1100	[thread overview]
Message-ID: <20170208232213.GH65698@eureka.lemis.com> (raw)
In-Reply-To: <04c401d2825d$d0758da0$7160a8e0$@ronnatalie.com>

On Wednesday,  8 February 2017 at 17:50:57 -0500, Ron Natalie wrote:
> Amusingly in the UNIVAC FIELDDATA character set.   The @ had the value zero
> (and was called the master space).
> It's sort of like making NUL the command character :)

Well, except that there were no non-printing characters in Fieldata.

> Amusingly UNIVAC had their own punched card format (same size card,
> which was by the way, the size of a dollar bill in Hollerith's day)
> but used two banks of 45 round holes for 90 columns.

Yes, I heard of them, but they didn't seem to be a commercial success.
I worked with UNIVAC kit from 1973 to 1977, on the 1108/1106 and the
494, but I never saw any card like that.  They also had a very nice
card punch, the VIP, that buffered a card content and only punched
when you released the card, thus enabling erasures.  But it used
standard IBM format cards.

> -Ron "I had a cat named @FURPUR" Natalie

:-)

Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170209/18593a3a/attachment.sig>


  reply	other threads:[~2017-02-08 23:22 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 18:06 ron minnich
2017-02-08 18:08 ` A. P. Garcia
2017-02-08 18:17 ` arnold
2017-02-08 23:39   ` Steve Johnson
2017-02-08 23:52     ` Dave Horsfall
2017-02-09  2:11       ` Corey Lindsly
2017-02-09  2:46         ` Dave Horsfall
2017-02-09  2:53           ` Corey Lindsly
2017-02-09  4:38           ` Warner Losh
2017-02-09  2:47       ` Steve Nickolas
2017-02-09  4:55         ` Steve Johnson
2017-02-09 11:59           ` Michael Kjörling
2017-02-09 21:56             ` Dave Horsfall
2017-02-10  0:17               ` Dan Cross
2017-02-10  1:58                 ` Dave Horsfall
2017-02-10  2:46                   ` Nemo
2017-02-10  2:49                     ` Dave Horsfall
2017-02-10  9:30                   ` arnold
2017-02-10  9:19               ` arnold
2017-02-09 12:18           ` Brantley Coile
2017-02-09 13:31             ` Nick Downing
2017-02-08 22:45 ` Greg 'groggy' Lehey
2017-02-08 22:50   ` Ron Natalie
2017-02-08 23:22     ` Greg 'groggy' Lehey [this message]
2017-02-09 12:12     ` Michael Kjörling
2017-02-09 12:26       ` Lars Brinkhoff
2017-02-09 14:37         ` Random832
2017-02-09 14:49           ` Random832
2017-02-09 12:31       ` Paul Ruizendaal
2017-02-09 13:07         ` Steffen Nurpmeso
2017-02-08 22:51   ` ron minnich
2017-02-08 23:22     ` Greg 'groggy' Lehey
     [not found] <mailman.204.1486594285.3779.tuhs@minnie.tuhs.org>
2017-02-09  0:03 ` Paul McJones
2017-02-09  2:28   ` Marc Rochkind
2017-02-09 13:11   ` Tony Finch
2017-02-09 14:44 Noel Chiappa
2017-02-09 16:51 ` Steffen Nurpmeso
2017-02-09 19:36   ` Steffen Nurpmeso
2017-02-09 21:14 Doug McIlroy
2017-02-10 17:39 ` Steffen Nurpmeso

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=20170208232213.GH65698@eureka.lemis.com \
    --to=grog@lemis.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).