🚀 go-pugleaf

Stefan Ludwig wrote:
> [deleted]
> 
> The solution most in the "Spirit of Oberon" would be to drop WITH on pointers
> altogether.
> This was suggested in Szyperski's "ETHOS" thesis and discussed at the Institute
> at length. The reason we left it the way it is, was that too much System3 code
> would have needed a rewrite.
> 
> I strongly advocate dropping WITH on pointers in commercial compilers.
> It's a hole in the type system, and it needs to be plugged!

XDS Oberon-2 (starting from v2.12) reports an error if the value of pointer may be changed
inside WITH, like in 

TYPE 
  P = POINTER TO R;
  R = RECORD i: INTEGER END;
  P1 = POINTER TO R1;
  R1 = RECORD (R) n: INTEGER END;

PROCEDURE proc1(p: P);
  PROCEDURE proc2;
  BEGIN
    p:=NIL;
  END proc2;
BEGIN
  WITH p: P1 DO
    proc2;
  END;
END proc1;

I think it is better solution then dropping WITH on pointers.

-- Alex