[Oberon] SystemV- Heap + Module Space

[Skulski, Wojciech]

Chris wrote:

> If possible, the logic that maps error codes onto error messages should be located in the module where the error codes are defined. Then the client call could be just:

The next logical step would be to move error messages to a "resource file" which would be read by the module where the error codes are defined. This could be used to provide multilingual capabilities at a relatively low implementation cost. The non-English characters probably can be handled by the Oberon font mechanism. 

Implementing error messages in languages other than English is probably not that important. But applications are another matter. Moving the string constants to resource files could lead to multilingual applications. I guess it has been done many times in the past.

Wojtek