[Oberon] System V5 - Definitions and Implementations

Tomas Kral thomas.kral at email.cz
Sun Apr 10 16:52:15 CEST 2016


Chris, All,

Thanks, now I can see, dropping separate interface definitions favours
the point of security, version checking, assuring integrity in time of
the entire application development.

Tomas

-- 
Tomas Kral <thomas.kral at email.cz>

On Sun, 2016-04-10 at 09:27 +0930, Chris Burrows wrote:
> > -----Original Message-----
> > From: Oberon [mailto:oberon-bounces at lists.inf.ethz.ch] On Behalf Of
> > thomas.kral at email.cz
> > Sent: Sunday, 10 April 2016 1:21 AM
> > To: ETH Oberon and related systems
> > Subject: [Oberon] System V5 - Definitions and Implementations
> > 
> > It is a very descriptive aid for documenting, however how can
> > Definitions be used from a programmer's point of view?
> > 
> 
> In Oberon (unlike its predecessor Modula-2) Definition modules are no longer
> required from a programming point of view. For an account of how and why
> this evolution occurred refer to the paper titled "Modula-2 and Oberon" by
> Niklaus Wirth:
> 
> http://www.inf.ethz.ch/personal/wirth/Articles/Modula-Oberon-June.pdf
> 
> Regards,
> Chris
> 
> Chris Burrows
> CFB Software
> http://www.astrobe.com
> 
> 
> 
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon


More information about the Oberon mailing list