Features of Modula that would have been nice to have in Pascal

In fact, as a language, I liked Modula better than Pascal. But Modula never got the popularity of Pascal; I don't know why. The features that I liked about Modula and which are missing in Pascal are mentioned on this page.

Note: Modula is very much like Pascal. The reason being that Modula was designed/developed by the same person (Wirth) who 'invented' Pascal; Modula was meant to be the 'successor' of Pascal.

1. The syntax of Pascal concerning the use of the keywords begin and end is sometimes a bit confusing. The rules that Modula has for this are a lot more elegant:
   • An if statement always ends with end but never needs a begin.
     Example:

       if a >= b
       then
         max := a
       else
         max := b
       end;

     Whether there is one statement or more statements in the then part (or the else part) makes no difference with respect to the use of begin and end.
   • The same goes for for statements and while statements:
     There's always a do, never a begin and always an end. Regardless of the number of statements in the loop.
   • Is the keyword begin then never used at all? Yes it is: subroutines (procedures and functions; and programs as well) start with begin and end with end. Just like Pascal.
2. Importing stuff from units is done explicitly.
   Where Object Pascal has (for example)

   uses Graphics, SysUtils, Windows;

   Modula has:

   from Graphics import TBitmap;
   from SysUtils import IntToStr, Exception;
   from Windows import GlobalAllocPtr;
   

   This ensures that all identifiers that are used in a module / unit are always declared inside this unit and there is no ambiguity about 'double' identifiers that are exported by multiple units (TBitmap is an example of that).
   It makes it a lot easier to find where a certain identifier 'comes from' and what it means.
   I really wished Object Pascal had a similar feature.