From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] I just noticed all the cfont aka C++ in research
Date: Thu, 6 Apr 2017 10:21:38 +0800 [thread overview]
Message-ID: <F79769A5-2991-487F-85F9-CA026C1A2868@superglobalmegacorp.com> (raw)
In-Reply-To: <CAGfO01xsyAWj=X=yUuC3hfbc+_=7606SP9X5bdCC6aS15c4FNg@mail.gmail.com>
I need to get one of those new fangled graphical terminals working!
On April 6, 2017 10:20:26 AM GMT+08:00, Noel Hunt <noel.hunt at gmail.com> wrote:
>> Or that emacs was in the v9 tree, in the religious wars
>> I always imagined NJ being more vi.
>
>
>I would be very much surprised if jim/sam was not the editor
>of choice (apart from Ken Thompson who seemed content with
>'ed').
>
>
>
>On Thu, Apr 6, 2017 at 12:15 PM, Jason Stevens <
>jsteve at superglobalmegacorp.com <mailto:jsteve at superglobalmegacorp.com>
>>
>wrote:
>
>
>I suppose that it would make sense that all of AT&T's leading edge
>projects would use research Unix. I've always heard of the original C++
>to C translator but this is the first time I've actually seen it.
>
>It doesn't look like it had the wide scale following that C or Fortan
>had at this point.
>
>Sadly my experience with C++ was mostly tied to Borland on the micro in
>early 90's, which makes it look mature compared to these early
>versions.
>
>It's great finding stuff like this in the tree hiding in plain sight,
>if
>only you know what to look for. ( http://unix.
><http://unix.superglobalmegacorp.com/cgi-bin/cvsweb.cgi/researchv9/cmd/c
>front/?cvsroot=rv9>
>superglobalmegacorp.com/cgi-bin/cvsweb.cgi/researchv9/cmd/cfront/?cvsroo
>t=rv9)
>
>Or that emacs was in the v9 tree, in the religious wars I always
>imagined NJ being more vi.
>
>Thanks again for making this release happen!
>
>--
>Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170406/50c01105/attachment-0001.html>
next prev parent reply other threads:[~2017-04-06 2:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 2:15 Jason Stevens
2017-04-06 2:20 ` Noel Hunt
2017-04-06 2:21 ` Jason Stevens [this message]
2017-04-06 6:57 ` [TUHS] Unix emacs at Bell Labs and elsewhere Erik E. Fair
[not found] <mailman.721.1491445316.3779.tuhs@minnie.tuhs.org>
2017-04-06 2:42 ` [TUHS] I just noticed all the cfont aka C++ in research Paul McJones
2017-04-06 3:20 Jason Stevens
2021-02-06 2:57 [TUHS] Typing tutors Will Senn
2021-02-06 16:55 ` Clem Cole
2021-02-06 17:22 ` Ron Natalie
2021-02-06 17:29 ` Clem Cole
2021-02-06 17:33 ` Mary Ann Horton
2021-02-06 17:47 ` Ron Natalie
2021-02-06 18:06 ` Clem Cole
2021-02-06 22:38 ` Dave Horsfall
2021-02-06 22:47 ` Niklas Karlsson
2021-02-07 0:25 ` John Cowan
2021-02-08 22:20 ` Dave Horsfall
2021-02-08 22:58 ` David Barto
2021-02-08 23:01 ` Clem Cole
2021-02-07 17:43 ` Mary Ann Horton
2021-02-07 19:28 ` Dan Cross
2021-02-07 21:32 ` Nemo Nusquam
2021-02-07 23:17 ` Henry Bent
2021-02-07 23:55 ` Steve Nickolas
2021-02-08 0:56 ` Henry Bent
2021-02-08 5:15 ` Erik E. Fair
2021-02-08 5:33 ` Steve Nickolas
2021-02-08 15:54 ` Will Senn
2021-02-08 5:29 ` Doug McIntyre
2021-02-08 20:41 ` Andrew Newman
2021-02-06 18:56 ` David Barto
2021-02-08 21:50 ` Dave Horsfall
2021-02-09 16:29 ` Mary Ann Horton
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=F79769A5-2991-487F-85F9-CA026C1A2868@superglobalmegacorp.com \
--to=jsteve@superglobalmegacorp.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).