[Oberon] OP2 Vs Wirth's compiler.

[Srinivas Nayak]

Dear All,

Many many thanks for the insight into OP2.


With thanks and best regards,

Yours sincerely,
Srinivas Nayak

Home: http://www.mathmeth.com/sn/
Blog: http://srinivas-nayak.blogspot.in/

On 07/31/2017 09:56 PM, Andreas Pirklbauer wrote:
> The latest RISC5 compiler handles this similar to the original Oberon compiler on Ceres: one single key per module. Thus, when the interface of a module is changed, *all* clients are invalidated. In the specific implementation, the key is simply the sum of all bytes in the symbol file, i.e. really is a checksum.
>
>
> See procedure ORS.Export athttp://www.inf.ethz.ch/personal/wirth/ProjectOberon/Sources/ORB.Mod.txt  .
>
>
> AP
>
>
>
> --------------
>
> *Josef Templ*josef.templ at gmail.com<mailto:oberon%40lists.inf.ethz.ch?Subject=Re:%20Re%3A%20%5BOberon%5D%20OP2%20Vs%20Wirth%27s%20compiler.&In-Reply-To=%3CCAMfW0Z0oJ%3D%2BoUyiDeLm4CG7B1W%2B8D0DYCjpcJhq%2BjdD3EC0MVQ%40mail.gmail.com%3E>
> /Mon Jul 31 15:52:13 CEST 2017/
>
>   * Previous message:[Oberon] OP2 Vs Wirth's compiler. <http://lists.inf.ethz.ch/pipermail/oberon/2017/010804.html>
>   * Next message:[Oberon] Re (2): Italicization of comments and emboldening of keywords. <http://lists.inf.ethz.ch/pipermail/oberon/2017/010797.html>
>   * *Messages sorted by:*[ date ] <http://lists.inf.ethz.ch/pipermail/oberon/2017/date.html#10807>[ thread ] <http://lists.inf.ethz.ch/pipermail/oberon/2017/thread.html#10807>[ subject ] <http://lists.inf.ethz.ch/pipermail/oberon/2017/subject.html#10807>[ author ] <http://lists.inf.ethz.ch/pipermail/oberon/2017/author.html#10807>
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Besides the abstract syntax tree construction, one difference between OP2
> and the original NW Oberon
> compiler is the compatibility checking across module boundaries.
> In OP2 there is a separate key (fingerprint) per exported object while in
> the original compiler there is a single key
> per module. Thus, whenever anything in a module is changed all clients are
> invalidated. In OP2 only clients that
> are using the changed object are invalidated. I don't know how this is
> handled in the latest RISC5 compiler.
>
> - JT
>
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>