Astrobe Forum

A wild guess - maybe 3x - 4x more effort.

The semantics of exported pointer variables is subtle though. Consider the following module: MODULE M; TYPE T* = POINTER TO RECORD x*: INTEGER END; VAR p*: T; q*: POINTER TO RECORD x*: INTEGER END; END M. In a client module the field M.p.x can be modified by a variable of type M.T whereas the field...

kevinhely wrote:Wirth said it was an oversight to leave the "D" business in the report. It will be removed shortly.

It has now been removed.

The most recent (dated 22 Feb 2014) published copy of the Oberon Report (Revision 1.10.2013) now says: Variables are always exported in read-only mode. instead of: Variables cannot be exported, with the exception of those of scalar types in read-only mode. Array and Record variables can be exported ...

The attached example program for the LPCXpresso LPC1769 shows how you can use the Serial functions RxReady and TxReady to avoid blocking. After you have uploaded the program the led will start flashing once per second (500ms on and 500ms off). Open the Astrobe Terminal window and click on the Reset ...

Good question! I'll make sure a section is added to the Debugging section of the documentation for the next release. For now, all the information you should need is here: The strategy that you used was very successful as you managed to identify the source code line with the problem - that is usually...

Thank you for reporting the problem. It seems that there is an error in the LPC1769 MCU.mod library file. Try replacing the line: with (i.e. there is an extra trailing 0)

After working with Prof Wirth's latest Oberon for FPGA compiler, and receiving replies to a couple of questions I realise that my last reply, and probably some of my earlier posts in this discussion, were incorrect. The following is actually legal Oberon code because PROCEDURE Q is a local variable ...

I can see why you ask - but it is allowed. While it is true that Q is declared locally in P, the identifier (in this case Q) that represents the name of a procedure is also visible in its own scope. Note that if that weren't true, the following would be possible: PROCEDURE Q; VAR Q: INTEGER; BEGIN ....

We have now decided that when we release the version of Astrobe which conforms to Oberon Rev 1.10.2013 the constants 0 .. 255 will be compatible with BYTE and INTEGER variables in assignments, but will be treated as INTEGERs when their type cannot be determined by the context (e.g. as parameters to ...