<head>
<title></title>
</head>
<body>
<div class="userStyles" style=" font-family: Arial; font-size: 12pt; color: #000000;">It appears that we disagree on the semantics of the quoted sentence, specifically on the denotation of the word "globally".<br>
<br>
--John R. Strohm
<footer class="replyforwardcontainer"><br>
<span>On Sun, 10 Dec 2023 17:12:41 +0100, August Karlstrom <fusionfile@gmail.com> wrote:</span><br>
<br>
On 2023-12-10 15:29, strohm@airmail.net wrote:<br>
> In the example at hand, as I read "In addition to its formal<br>
> parameters and locally declared objects, the objects declared<br>
> globally are also visible in the procedure." on page 12 of the<br>
> Oberon-07 report at Microsoft Word - Oberon07.Report.doc (ethz.ch)<br>
> <https: oberon="" oberon07.report.pdf="" people.inf.ethz.ch="" wirth="">, items<br>
> declared at module M scope are visible inside Q, as are items<br>
> declared at procedure M.P scope.<br>
<br>
The quoted sentence says exactly that only strictly local and global<br>
objects (constants, types, variables and procedures) are visible in a<br>
given procedure, so items declared in the scope M.P are not visible in<br>
the scope M.P.Q. The document "Oberon at a Glance" says "No access to<br>
variables in outer procedures" but that's just a reflection of the<br>
Project Oberon 2013 compiler enforcing this only for variables.<br>
<br>
https://people.inf.ethz.ch/wirth/Oberon/OberonAtAGlance.pdf<br>
<br>
<br>
August<br>
--<br>
Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems<br>
https://lists.inf.ethz.ch/mailman/listinfo/oberon</https:><br>
</footer>
</div>
</body>