April 2017 - Oberon - mailman3.inf.ethz.ch

FPGA Oberon - Definition Module Tool
by thomas.kral＠email.cz 08 Oct '18

08 Oct '18

Hi, I am thinking of a simple tool that could extract definition info from *.Mod and produce respective *.Def file. Definition files can be quickly looked at, to remind a programmer of the interface *.Mod modules export. While on Linux one could use grep $ grep PROCEDURE\ * *.Mod.txt to obtain info at least about procedures, but how about exported types and variables? 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. Tomas

5 11

FPGA - Save / Restore OBERON.FS
by Andreas Pirklbauer 22 Jul '17

22 Jul '17

There will be an enhanced Oberon file system in Experimental Oberon offering, amongst other things, larger file sizes.________________________________________ > From: Skulski, Wojciech skulski at pas.rochester.edu > Sent: Thu Apr 20 06:42:54 CEST 2017 > My biggest concern about Oeron FS is its limited size. > Wojtek

4 10

FPGA - SET initialisation
by Tomas Kral 22 May '17

22 May '17

Hi, Reading `SET - neglected data type', I was wondering, how I could best initialise a SET variable. VAR b: BYTE, i: INTEGER, s: SET; ... SYTEM.GET(adr, s); (* reading 4 bytes from adr, easiest but adr MOD 4! *) ... SYTEM.GET(adr, i); s := {i}; (* same result as above? *) ... (* provided adr MOD = 0 *) SYTEM.GET(adr+0, b); s := {b}; (* same result as above? *) SYTEM.GET(adr+1, b); ASL(s,8); s := s + {b}; SYTEM.GET(adr+2, b); ASL(s,8); s := s + {b}; SYTEM.GET(adr+3, b); ASL(s,8); s := s + {b}; Tomas

4 12

Modulus on negative number
by Srinivas Nayak 15 May '17

15 May '17

Dear All, Recently I come across modulus on a negative number. Will it produce a negative number or positive? Someone says both are correct! http://stackoverflow.com/a/4403556 Which one is mathematically correct? Surprisingly different languages calculate it differently even! What is Oberon's way? With thanks and best regards, Yours sincerely, Srinivas Nayak Home: http://www.mathmeth.com/sn/ Blog: http://srinivas-nayak.blogspot.in/

9 17

FPGA - ORP.Compile * `marked viewer'
by Andreas Pirklbauer 30 Apr '17

30 Apr '17

PROCEDURE MarkedViewerText* (): Texts.Text; VAR V: Viewers.Viewer; T: Texts.Text; BEGIN V := Oberon.MarkedViewer(); IF (V.dsc # NIL) & (V.dsc.next IS TextFrames.Frame) THEN T := V.dsc.next(TextFrames.Frame).text ELSE T := NIL END ; RETURN T END MarkedViewerText; Use in ORP.Compile: ELSIF S.c = "*" THEN T := MarkedViewerText(); IF (T # NIL) & (T.len > 0) THEN ORS.Init(T, 0); Module END END

1 0

FPGA - LONG WORD memory access
by Tomas Kral 30 Apr '17

30 Apr '17

Hi, Is allowed to address 4byte integers on odd memory address, or does it have to be on even boundaries only, aligned on MOD 4? I remember from other platforms, namely 68K, words or longs on even address only. Many thanks Tomas

3 6

FPGA - ORP.Compile * `marked viewer'
by Andreas Pirklbauer 25 Apr '17

25 Apr '17

Paul, I have to disappoint you. I’m not engaging in a race to indiscriminately add new features to the Oberon system (that would be against the very spirit of Oberon, wouldn’t it?). Thinking about it though, I would probably recommend to refrain from adding a procedure MarkedViewerText() to module Oberon because it would either require module TextFrames to be imported in module Oberon (which however is the top module of the outer core and therefore is not supposed to contain TextFrames - wrong place!) or require placing MarkedViewerText within ORP itself, which in turn would trigger the import of modules Viewer and TextFrames. Not pretty either. The only remaining option then would be to create a new System.Compile command just for that one purpose (namely of accepting the “*” option) and move MarkedViewerText up to module System instead. Three unappealing options! But if one really *wanted* to add the “*” option, it would of course be straightforward: PROCEDURE MarkedViewerText* (): Texts.Text; VAR V: Viewers.Viewer; T: Texts.Text; BEGIN V := Oberon.MarkedViewer(); IF (V.dsc # NIL) & (V.dsc.next # NIL) & (V.dsc.next IS TextFrames.Frame) THEN T := V.dsc.next(TextFrames.Frame).text ELSE T := NIL END ; RETURN T END MarkedViewerText; and then in ORP.Compile: ELSIF S.c = "*" THEN T := MarkedViewerText(); IF (T # NIL) & (T.len > 0) THEN ORS.Init(T, 0); Module END END Then one can first designate any (text) frame as operand by placing the star marker in it and activate the command ORP.Compile * . It does work. But does one need it? Again, I would not recommend adding it. If someone finds an elegant solution to this, I’d reconsider. And if someone forced me to add it, I would probably go the route via a new command System.Compile and move MarkedViewerText up to module System (even though it does not belong there). This would keep both modules Oberon and ORP free of unwanted imports. Andreas ---------------------------------------- Paul Reed paulreed at paddedcell.com <http://paddedcell.com/> Tue Apr 25 16:16:14 CEST 2017 Hi Tomas, Not sure if useful, but is there a way to add * marked viewer as a parameter to ORP? > ORP.Compile ~ is there > ORP.Compile ^ (make sense?) > ORP.Compile @ is there > ORP.Compile * to add I assume Prof. Wirth removed (or didn't add, he seems to write a lot of his compilers freshly from scratch) the "marked viewer" version of the compiler parameter handling because it removes the need for dependencies on the imports Viewers and TextFrames (and the fiddly walk down the viewer hierarchy to find the marked text). As an exercise you could add the feature back in to ORP.Mod if you wish, by referring to the code in the original edition, in Compiler.Mod. (BTW you may notice that Edit.Locate has been changed too, to use the FocusViewer instead of the MarkedViewer - though not for the same reason). It might perhaps have been better, in hindsight, if the Oberon module had exported a function Oberon.MarkedViewerText(). No doubt Andreas has already added it... ;-) HTH Paul

1 0

FPGA - Inline Patterns
by Tomas Kral 25 Apr '17

25 Apr '17

Hi, EDIT I am toying with ETH `Bitmaps.Mod' now compiled under RISC/FPGA, and partly ported, supporting so far B&W DisplayBlock (replace/paint/invert), Copy(replace), and CopyBlock(replace). $..$ helps with me testing Bitmaps.CopyPattern, I pass various patterns defined in Display.Mod to it. In various languages, FORTRAN, BASIC, there is DATA statement. I understand these are frowned upon in Wirthian true language sense. But If I needed a persistent constant block of data, could I use CONST somehow? What is the recommended way? Tomas On Mon, 24 Apr 2017 20:34:29 +0200 Andreas Pirklbauer <andreas_pirklbauer(a)yahoo.com> wrote: > A string enclosed by $ . . . $, as is used in modules Display or > Input for example, is called HexString (see ORS.HexString). HexString > is a little feature that elegantly addressed a small problem, but it > was never intended to be widely used. That’s why it is not published > in the language report - which means that it *is* officially not part > of the language. But if you know what you are doing, you can - it > likely won’t go away. And if it does, well, then you’d notice ;-) > Andreas > > ---------------------------------------------------------------------------------- > > Jörg joerg.straube at iaeth.ch Mon Apr 24 18:10:34 CEST 2017 > > Officially, the Oberon language only offers expression for constant > > "array of chars”, called string constants. > > The constant "array of bytes" you are refering to is a feature of > > the compiler, not described in the language as far as I know. > > > It is also used eg. in the keyboard driver to translate keyboard > > strokes to chars. > > > br > > Jörg > > ---------------------------------------------------------------------------------- > > > Am 24.04.2017 um 17:53 schrieb Tomas Kral <thomas.kral at email.cz > > <https://lists.inf.ethz.ch/mailman/listinfo/oberon>>: > > > > Hi, > > > > I have just discovered this interesting and useful construct, found > > in `Display.Mod', defining a pattern. > > > > block := SYSTEM.ADR($0808 FFFF C3C3 C3C3 FFFF$); > > > > pattern = w(byte) h(byte) {raster(byte)} > > > > block* is exported, so can also be used in user modules. > > > > Tomas > > -- > > Oberon at lists.inf.ethz.ch > > <https://lists.inf.ethz.ch/mailman/listinfo/oberon> mailing list > > for ETH Oberon and related systems > > https://lists.inf.ethz.ch/mailman/listinfo/oberon > > <https://lists.inf.ethz.ch/mailman/listinfo/oberon> > -- Oberon(a)lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon

2 1

FPGA - ORP.Compile * `marked viewer'
by Tomas Kral 25 Apr '17

25 Apr '17

Hi, Not sure if useful, but is there a way to add * marked viewer as a parameter to ORP? ORP.Compile ~ is there ORP.Compile ^ (make sense?) ORP.Compile @ is there ORP.Compile * to add Tomas

2 1

FPGA - Inline Patterns
by Andreas Pirklbauer 25 Apr '17

25 Apr '17

A string enclosed by $ . . . $, as is used in modules Display or Input for example, is called HexString (see ORS.HexString). HexString is a little feature that elegantly addressed a small problem, but it was never intended to be widely used. That’s why it is not published in the language report - which means that it *is* officially not part of the language. But if you know what you are doing, you can - it likely won’t go away. And if it does, well, then you’d notice ;-) Andreas ---------------------------------------------------------------------------------- > Jörg joerg.straube at iaeth.ch Mon Apr 24 18:10:34 CEST 2017 > Officially, the Oberon language only offers expression for constant "array of chars”, > called string constants. > The constant "array of bytes" you are refering to is a feature of the compiler, > not described in the language as far as I know. > It is also used eg. in the keyboard driver to translate keyboard strokes to chars. > br > Jörg ---------------------------------------------------------------------------------- > Am 24.04.2017 um 17:53 schrieb Tomas Kral <thomas.kral at email.cz <https://lists.inf.ethz.ch/mailman/listinfo/oberon>>: > > Hi, > > I have just discovered this interesting and useful construct, found in > `Display.Mod', defining a pattern. > > block := SYSTEM.ADR($0808 FFFF C3C3 C3C3 FFFF$); > > pattern = w(byte) h(byte) {raster(byte)} > > block* is exported, so can also be used in user modules. > > Tomas > -- > Oberon at lists.inf.ethz.ch <https://lists.inf.ethz.ch/mailman/listinfo/oberon> mailing list for ETH Oberon and related systems > https://lists.inf.ethz.ch/mailman/listinfo/oberon <https://lists.inf.ethz.ch/mailman/listinfo/oberon>

3 2