O2 & security hole in BB

From: [at]} <>
Date: 1 May 2001 09:58:05 MDT

Wecks explanation is that O2 introduces a security hole in BB. Theoretically
it would be possible to create a language, which is vertically compatible with
O2 but still maps naturally to CP.

Ill call the language (temporarly) O3. Now Ill define tha mapping:


O3
TYPE R1 = RECORD END;

=>

CP:
TYPE R1 = EXTENSIBLE RECORD END;


O3:
TYPE R1 = FINAL RECORD END

=>

CP:
TYPE R1 = RECORD END;


O3:
PROCEDURE (VAR Self: R1) P1;

=>

C3:
PROCEDURE (VAR Self: R1) P1, NEW;



O3:
PROCEDURE (VAR Self: R1), OVERRIDE;

=>

CP:
PROCEDURE (VAR Self: R1);



____________________________________________________________________
Get free email and a permanent address at
http://www.netaddress.com/?N=1
Received on Tue May 01 2001 - 15:58:05 UTC

This archive was generated by hypermail 2.3.0 : Thu Sep 26 2013 - 06:27:44 UTC