Computer Old Farts Forum
 help / color / mirror / Atom feed
From: sauer at technologists.com (Charles H Sauer)
Subject: [COFF] What languges would you like to learn?
Date: Thu, 26 Dec 2019 15:57:06 -0600	[thread overview]
Message-ID: <96a7d832-d643-2e3f-95a0-00441df01c2e@technologists.com> (raw)
In-Reply-To: <20191226213703.GN3839@mcvoy.com>



On 12/26/2019 3:37 PM, Larry McVoy wrote:
> On Fri, Dec 27, 2019 at 07:28:27AM +1000, David Arnold wrote:
>> C++ is several different languages in one compiler.
> 
> Bingo, well said.  I find kitchen sink languages like that awful.
> It's not what you put in, it's what you don't let in.
> 
> As you said, it takes a lot of discipline to use the right subset
> which makes you wonder why there isn't a language that is the right
> subset.

PL.8 (https://en.wikipedia.org/wiki/PL/8) springs to mind. I can't say 
that it was the right or wrong subset of PL/I. I do know that I wrote a 
major simulation environment in PL/I while avoiding much of PL/I. I 
never used PL.8 myself, just learned it enough to write a PL.8 to C 
conversion tool that some AIX folks found useful.

Though the Wikipedia page makes PL.8 sound successful, it is hard to 
imagine that more than a small minority of folks chose PL.8 over PL/I. 
Even assuming PL.8 was the right subset, it would have struggled to 
overcome entrenched PL/I.


  reply	other threads:[~2019-12-26 21:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 23:27 cym224
2019-12-24  9:54 ` thomas.paulsen
2019-12-24 16:28 ` toby
2019-12-24 16:35   ` lm
2019-12-24 17:50     ` 
2019-12-24 18:04       ` lm
2019-12-25  3:34     ` dave
2019-12-25 16:02     ` cym224
2019-12-25 17:05     ` thomas.paulsen
2019-12-24 20:27 ` dave
2019-12-25 17:31 ` rtomek
2019-12-25 19:13   ` athornton
2019-12-26  0:23     ` me
2019-12-26  1:54       ` wobblygong
2019-12-26  3:44         ` dave
2019-12-26  4:00           ` lm
2019-12-26  5:43             ` wobblygong
2019-12-26 11:49               ` tih
2019-12-26 15:33                 ` lm
2019-12-26 16:34                 ` thomas.paulsen
2019-12-26 16:53                   ` lm
2019-12-27  3:00                 ` dave
2019-12-27  7:02                   ` thomas.paulsen
2019-12-26 17:57               ` bakul
2019-12-26 21:28                 ` davida
2019-12-26 21:37                   ` lm
2019-12-26 21:57                     ` sauer [this message]
2019-12-26 22:13                     ` 
2019-12-27  3:41                     ` bakul
2019-12-27  4:00                       ` lm
2019-12-27  4:28                         ` bakul
2019-12-26 22:16                   ` imp
2019-12-27  3:41                   ` bakul
2019-12-26 15:43         ` dfawcus+lists-coff
2019-12-27 17:46   ` cym224
2019-12-27 21:33     ` tih

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=96a7d832-d643-2e3f-95a0-00441df01c2e@technologists.com \
    --to=coff@minnie.tuhs.org \
    /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).