Benjamin Kowarsch

First off, I have both PIM3 and PIM4 and I'd be happy to send you the definitions of FileSystem. As for MacMETH, this is a very problematic compiler as far...

I figured I can post the definitions here: ```Modula-2 (* Source: PIM 3rd Edition, page 178 *) DEFINITION MODULE FileSystem (* S.E.Knudsen *) FROM SYSTEM IMPORT ADDRESS, WORD; TYPE Response...

```Modula-2 (* Source: PIM 4th Edition, page 161 *) DEFINITION MODULE FileSystem (* S.E.Knudsen *) FROM SYSTEM IMPORT ADDRESS, WORD; TYPE Flag = ( er, ef, rd, wr, ag, bm...

Please note that PIM defines WORD as the smallest addressable unit. In other words, PIM does not define any identifier called BYTE, but semantically, WORD is the same as BYTE....

Lastly, yes indeed, M2M was PIM2-only. You can also tell from the export list in the definition module. Only PIM2 allows exports in definition modules. PIM3 and PIM4 don't accept...

The FileSystem module of PIM is not really great design and as you can see from the two definitions I posted it also differs between PIM3 and PIM4. It is...

As for the question how compliant is ACK with PIM3 ... I have not done any specific testing for this but I read the various comments by the original developer...

Why would the license of M2PP matter? You say you are using sed which is also not BSD license compatible, and you don't seem to have any issue with that....

As for differences between Modula-2 dialects and compilers over time ... I don't know much about Occam but from your description it sounds like the language had undergone very significant...

FYI, one of the things on my to do list (albeit low priority) is a utility that would (1) remove all `EXPORT` directives from Modula-2 .def files, (2) remove any...