From: Dr Iain Maoileoin <iain@csp-partnership.co.uk>
To: Clem Cole <clemc@ccc.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>,
TUHS main list <tuhs@minnie.tuhs.org>,
Brian Walden <tuhs@cuzuco.com>
Subject: Re: [TUHS] [TUHS -> moving to COFF] # and the Preprocessor
Date: Wed, 8 Jan 2020 22:25:13 +0000 [thread overview]
Message-ID: <5BDC3682-F79F-449F-A815-A0C3F1184A21@csp-partnership.co.uk> (raw)
In-Reply-To: <CAC20D2Pd+gEu8AmsAjJ5vxT+GGfU8PyRXRD7Aux0v2-VUN0N8A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
> On 8 Jan 2020, at 16:02, Clem Cole <clemc@ccc.com> wrote:
>
> below... -- warning veering a little from pure UNIX history, but trying to clarify what I can and then moving to COFF for follow up.
>
> On Wed, Jan 8, 2020 at 12:23 AM Brian Walden <tuhs@cuzuco.com <mailto:tuhs@cuzuco.com>> wrote:
> ....
>
> - CMU's ALGOL68S from 1978 list all these ways --
> co comment
> comment comment
> pr pragmat
> pragmat pragmat
I remember that a pragma (at least in Algol68R (ICL 1900 series) and I would need to reread the formal definition to see if it was general) was not a comment.
It was a note to the compiler - which could choose to use it or lose it.
> # (comment symbol) comment
> :: (pragmat symbol) pragmat
> (its for UNIX v6 or v7 so not surprising # is a comment)
> http://www.softwarepreservation.org/projects/ALGOL/manual/a68s.txt/view <http://www.softwarepreservation.org/projects/ALGOL/manual/a68s.txt/view>
>
[-- Attachment #2: Type: text/html, Size: 2739 bytes --]
prev parent reply other threads:[~2020-01-08 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 16:02 Clem Cole
2020-01-08 22:25 ` Dr Iain Maoileoin [this message]
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=5BDC3682-F79F-449F-A815-A0C3F1184A21@csp-partnership.co.uk \
--to=iain@csp-partnership.co.uk \
--cc=clemc@ccc.com \
--cc=coff@tuhs.org \
--cc=tuhs@cuzuco.com \
--cc=tuhs@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).