<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Sprechblasentext Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.SprechblasentextZchn
{mso-style-name:"Sprechblasentext Zchn";
mso-style-priority:99;
mso-style-link:Sprechblasentext;
font-family:"Tahoma","sans-serif";}
span.E-MailFormatvorlage20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Thomas,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">what about this one:
<a href="https://sourceforge.net/p/oberon/oberonv4/ci/master/tree/UV4/Def.Mod">https://sourceforge.net/p/oberon/oberonv4/ci/master/tree/UV4/Def.Mod</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">--<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> Bernhard<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> thomas.kral@email.cz [mailto:thomas.kral@email.cz]
<br>
<b>Sent:</b> Monday, March 27, 2017 1:14 PM<br>
<b>To:</b> ETH Oberon and related systems<br>
<b>Subject:</b> Re: [Oberon] FPGA Oberon - Definition Module Tool<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi Wojciech,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I am looking in my copy of V4, does not seem to contain `Def.Mod'. Where it comes from in your version?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">$ tar -tzf ProjectOberon.V4.tar.gz | grep Def.Mod<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Many thanks<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Tomas<o:p></o:p></p>
</div>
<p><span lang="EN-US">---------- Původní zpráva ----------<br>
Od: Skulski, Wojciech <</span><a href="mailto:skulski@pas.rochester.edu"><span lang="EN-US">skulski@pas.rochester.edu</span></a><span lang="EN-US">><br>
Komu: ETH Oberon and related systems <</span><a href="mailto:oberon@lists.inf.ethz.ch"><span lang="EN-US">oberon@lists.inf.ethz.ch</span></a><span lang="EN-US">><br>
Datum: 25. </span>3. 2017 15:53:54<br>
Předmět: Re: [Oberon] FPGA Oberon - Definition Module Tool<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">> I am thinking of a simple tool that could extract definition info from *.Mod
<br>
<br>
How about Def.Mod which is available under Oberon System V4? <br>
<br>
Right click on "Def.Show Def.Mod" opens a new viewer with the following: <br>
<br>
DEFINITION Def; (* CAS *) <br>
<br>
PROCEDURE Show; (* ( "*" | "^" | name ) [ "\P" ] --P option enforces plain text style *)
<br>
END Def. <br>
---------------------------------------------------------------- <br>
Def.Show Documents.Mod opens the following viewer: <br>
<br>
DEFINITION Documents; <br>
CONST <br>
profile = "Documents.Profile"; (* on startup all openers contained in this file are registered automatically *)
<br>
TYPE <br>
Opener = POINTER TO RECORD <br>
pattern-, cmd-: ARRAY 32 OF CHAR; <br>
next-: Opener <br>
END; <br>
VAR <br>
openers-: Opener; <br>
PROCEDURE Open; (* ^ | name Opens the specified file with the registered opener, if no specific opener is found for the extension of the file, Edit.Open is used. *)
<br>
PROCEDURE RegisterOpener (pattern, command: ARRAY OF CHAR); (* Registers the opener command for the pattern. Openers that are registered earlier can be overwritten by (more specific) openers registered later. *)
<br>
PROCEDURE RegisterOpeners; (* ^ | filename Registers all the openers contained in the specified file. Their precedence is as they appear in the file. *)
<br>
END Documents. <br>
<br>
<span lang="EN-US">________________________________________ <br>
From: Oberon [oberon-bounces@lists.inf.ethz.ch] on behalf of </span><a href="mailto:thomas.kral@email.cz"><span lang="EN-US">thomas.kral@email.cz</span></a><span lang="EN-US"> [thomas.kral@email.cz]
<br>
Sent: Friday, March 24, 2017 7:52 AM <br>
To: ETH Oberon and related systems <br>
Subject: [Oberon] FPGA Oberon - Definition Module Tool <br>
<br>
Hi, <br>
<br>
I am thinking of a simple tool that could extract definition info from *.Mod and produce respective *.Def file.
</span>Definition files can be quickly looked at, to remind a programmer of the interface *.Mod modules export.
<br>
<br>
While on Linux one could use grep <br>
$ grep PROCEDURE\ * *.Mod.txt <br>
<br>
to obtain info at least about procedures, but how about exported types and variables?
<br>
<br>
I am looking for a recommended way how to simply code such a tool, is it a good idea to use `ORP' parser somehow for the task? I prefer to code it simple, does not have to be perfect, but should carry the idea.
<br>
<br>
<span lang="EN-US">Tomas <br>
-- <br>
</span><a href="mailto:Oberon@lists.inf.ethz.ch"><span lang="EN-US">Oberon@lists.inf.ethz.ch</span></a><span lang="EN-US"> mailing list for ETH Oberon and related systems
<br>
</span><a href="https://lists.inf.ethz.ch/mailman/listinfo/oberon"><span lang="EN-US">https://lists.inf.ethz.ch/mailman/listinfo/oberon</span></a>
<span lang="EN-US"><o:p></o:p></span></p>
</blockquote>
</div>
</div>
</body>
</html>