On Sat, 19 Jun 2021, at 15:03, Paul Gilmartin wrote:
> (where does "EXTERNAL:" in the Subject: come from?
I think some people's email systems (work ones?) flag incoming
emails from outwith their intranet that way. Then when they
reply to the thread the word "EXTERNAL" is in their reply, and
after that anyone-else's replies to their reply.
> Can it be suppressed?
Only if the listserv has configurable Subject editing, I expect ...
or if it can be forced to reinstate the original subject in every
reply it sends out. And that would be a problem when the
discussions go off-topic and people edit the Subject: usefully.
Some email/news clients can be set-up to elide words from
Subject lines (sometimes used to strip "Re: Re: Ad: RE:" etc
from Subject lines.
> On Sat, 19 Jun 2021 08:51:57 +0100, Jeremy Nicoll wrote:
> > ...
> >It made the compiler simpler to write, and solved the problem of
> >a compiler having to decide on nested ifs which one an else
> >belonged to (the "hanging else" problem - usually solved by
> >assuming an else belongs to the most recent if).
> >
> I'll repeat my preference strong closure. Even JCL recognized the
> wisdom of that convention. DO...END and {...} were a naive mistake.
I'm sorry, I don't know what you mean!
In my example the use of Algol's "begin" and "end" (or shorthand
forms "{" and "}") are only used when multiple statements are to
be treated as a single clause.
The important thing, from a programmer's pov is the difference
between
if <condition> do <clause>
and
if <condition> then <clause> else <clause>
where the compiler's lookahead in the parser sees, after the "if" and a
valid condition, either a "do" or a "then" token. In this language, "do"
is not a synonym for "begin" (Algol) or the way that "do" is used to
introduce a set of statements (Rexx).
In either case it will then expect the first <clause> but after that it
already knows whether there must not be, or must be, respectively,
an "else" and a second clause.
--
Jeremy Nicoll - my opinions are my own.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
