More generally, I'm taking about dispensing with begin-end in control statements, as Wirth did with Modula-2 and Oberon. It makes for clearer and much more readable code which has a pleasing symmetry about it.
You need to take this in context. Pascal was a hurried derivative of ALGOL-W, which was syntactically close to ALGOL-60 where the rule was that an if statement (etc.) controlled a single subsequent statement. That form was also consistent with the if /expression/, which selected one of two possible subsequent expressions for evaluation.
The dangling-else issue was identified and fixed in ALGOL-68, and as a member of the committee Wirth cannot claim ignorance of both the issue and its solution.
There are two corollaries to this. The first is that if Wirth had had even minimal exposure to COBOL he should have realised how problematic the various declaration sections were, and the extent to which they were already derided. As such, I would argue that CONST, TYPE, VAR and the rest should similarly require a BEGIN-END if they applied to multiple declarations.
The second is that the extremely uncomfortable mix of styles in Pascal "as currently spoken", where an if statement /requires/ a BEGIN-END to govern more than one subsequent statement but a CASE-ELSE-END is self-closing, is largely Borland's doing. However it would be unfair to absolve Wirth of all responsibility, since RECORD-END and REPEAT-UNTIL are his responsibility.
The bottom line is that we've inherited a Godawful mess.
MarkMLl