[Oberon] *****SPAM***** Re: *****SPAM***** Re: Oberon-2 type bound procedure scope

[strohm at airmail.net]

It appears that we disagree on the semantics of the quoted sentence, specifically on the denotation of the word "globally".

--John R. Strohm

On Sun, 10 Dec 2023 17:12:41 +0100, August Karlstrom <fusionfile at gmail.com> wrote:

On 2023-12-10 15:29, strohm at airmail.net wrote:
> In the example at hand, as I read "In addition to its formal
> parameters and locally declared objects, the objects declared
> globally are also visible in the procedure." on page 12 of the
> Oberon-07 report at Microsoft Word - Oberon07.Report.doc (ethz.ch)
> , items
> declared at module M scope are visible inside Q, as are items
> declared at procedure M.P scope.

The quoted sentence says exactly that only strictly local and global
objects (constants, types, variables and procedures) are visible in a
given procedure, so items declared in the scope M.P are not visible in
the scope M.P.Q. The document "Oberon at a Glance" says "No access to
variables in outer procedures" but that's just a reflection of the
Project Oberon 2013 compiler enforcing this only for variables.

https://people.inf.ethz.ch/wirth/Oberon/OberonAtAGlance.pdf


August
--
Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
https://lists.inf.ethz.ch/mailman/listinfo/oberon
 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20231210/f0939f04/attachment.html>