Marco van de Voort wrote:
In our previous episode, Mark Morgan Lloyd said:
I think that the one thing I'd suggest to everybody is that it would be
highly desirable if the dangling else fix were guaranteed to break
Pascal syntax. As such end if; etc. might be a better choice
If you start a different language, yes, the block system would be number one.
Do away
with oneline vs multiline blocks ambiguity in general. (and not just because
of ELSE).
Second would be a different procedure-block ending from just "end;" though the
M2 way
of end "procedurename" is unnecessary hard to maintain. end proc; or end
function would be just fine.
As usual that doesn't mean I want to micromanage. I don't have to end every
block in a specific way. As usual, bounding the major problem (don't let an
unterminated block
spill over function bounderies) is enough.
I came across an odd thing in a paper about ALGOL 60 the other day: "Any
character between the symbol end and the first semicolon or
end or else following this end is [comment] text." I've never ploughed
through the original documents and presume it's in there somewhere, but
it does seem like an attractive facility.
If you want to merely extend pascal, my fav feature would be qualified vs
unqualified import/export control I guesst.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
