Astrobe Forum

We don't have any immediate plans to develop a standard library module for CAN. Based on our experience, my recommendations when developing a new module like this are: Study the relevant chapter(s) of the User manuals for the microcontroller you are targeting. Look for application notes on the subje...

Sorry - I accidentally edited your message instead of replying to it :oops: I can think of several good reasons: minimal usefulness, uniformity / consistency / regularity (look at the confusion caused when variables were an exceptional case), simplification of the compiler, better performance (inter...

Mutually recursive procedures are still possible. The following compiles OK. P1 is a global procedure so it can be called from P2. P2 is local to P1 so it can be called from P1: MODULE Mutual; PROCEDURE P1; PROCEDURE P2; BEGIN P1 END P2; BEGIN P2 END P1; END Mutual. However you do not need to use ne...

Yes - the new compiler reports the error undefined identifier for your example the same as it does for any other object that is not visible in its scope.

We are now investigating what we need to do to be able to support the Cortex-M4. Initial tests will involve a couple of LPC4088-based boards.

For most cases we are treating compatible as meaning the same as far as BYTE and INTEGER are concerned in the Astrobe Oberon compiler that conforms to the 1.10.2013 revision. e.g. the following are allowed where b is a BYTE and i is an INTEGER: INC(i) INC(b) INC(b, i) INC(i, b) b := i + 1 i := b + 1...

We are testing how removing the visibility of intermediate local objects affects the earlier examples. The example that started this discussion now reports the error messages: undefined identifier for the references to x in the latest Oberon compiler being developed: MODULE Nested; PROCEDURE P; VAR ...

That's good as we had already removed it from the compiler

Good point. It is also still referenced in section 3. Vocabulary in assocation with the 'D' suffix on constants. However, LONGREAL was also removed from the list of pre-defined identifiers in Section 4, and as a possible type of argument to FLOOR in section 10.2. The SHORT and LONG type transfer fun...

Runtime checks such as these (and overflows etc.) are not requirements of the language report. They are left up to the discretion of the implementer. We haven't implemented them in the Astrobe compiler. We recommend the use of assertions as a problem-detection strategy for programmers who write code...