Computer Old Farts Forum
 help / color / mirror / Atom feed
From: cowan at ccil.org (John Cowan)
Subject: [COFF] Algol68 (was Re: [TUHS] Were cron and at done at the same time? Or one before the other?
Date: Thu, 17 Dec 2020 19:31:36 -0500	[thread overview]
Message-ID: <CAD2gp_TT_1DaSq56s+Grs-xSaNy8h3-x+h6H2m703gMH45uvKw@mail.gmail.com> (raw)
In-Reply-To: <8D8E8160-F6F9-461A-BDFD-0E0A0E4C1A2B@iitbombay.org>

On Thu, Dec 17, 2020 at 11:35 AM Bakul Shah <bakul at iitbombay.org> wrote:

> Funny how we seem to rehash the same things over the years!
>

Ars longa, vita brevis.

> In a 1988 comp.lang.misc thread when I expressed hope that "a major
> subset of Algol 68 with a new and concise syntax (sort of like C's)
> can make a very elegant, type safe and well rounded language.",


Thanks.  The URL is <
https://groups.google.com/u/2/g/comp.lang.misc/c/qkmB_3zuC7Y/m/-Bk9z-oZaqYJ
>.

> Piet
> van Oostrum[1] commented the combination of dynamic arrays *and*
> unions forced the use of GC in Algol68. Either feature by themselves
> wouldn't have required GC!


I can't find this anywhere in the thread or elsewhere in comp.lang.misc.
Do you have a reference?

In any case, I don't understand how a safe language with pointers can avoid
the need for *some* kind of GC.

[My exposure to Algol68 was when I had stumbled upon Brailsford and
> Walker's wonderful "Introductory Algol 68 programming"


Alas, I can only find this at one shady site, or in hardback at Amazon for
USD 20 which is a lot for a pig in a poke (no preview).



John Cowan          http://vrici.lojban.org/~cowan        cowan at ccil.org
"But I am the real Strider, fortunately," he said, looking down at them
with his face softened by a sudden smile.  "I am Aragorn son of Arathorn,
and if by life or death I can save you, I will."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20201217/8bd067c0/attachment.htm>


  reply	other threads:[~2020-12-18  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAC20D2PXZY9aWgDf-RknROs6JbKEUjzbQ2BRzfTgTR07pXni3g@mail.gmail.com>
     [not found] ` <88E7F8CE-DC08-44AB-BF12-EFD4C5958950@iitbombay.org>
     [not found]   ` <alpine.BSF.2.21.9999.2012150715040.25789@aneurin.horsfall.org>
     [not found]     ` <7e66e5eb-6cea-5403-a2cc-e8d93f038e66@gmail.com>
     [not found]       ` <CAD2gp_R3JjgqLK-sBzaga63-2Jp_Hx15bnxMDKxp4+aCOzYSiw@mail.gmail.com>
2020-12-17 16:35         ` bakul
2020-12-18  0:31           ` cowan [this message]
2020-12-18  1:25             ` bakul

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=CAD2gp_TT_1DaSq56s+Grs-xSaNy8h3-x+h6H2m703gMH45uvKw@mail.gmail.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).