[Oberon] Why macros were not implemented in oberon language?

Alexander Iljin ajsoft at yandex.ru
Mon Jul 7 12:08:02 CEST 2014

Hi, all!

> In a high level language, like Oberon, it doesn't make sense to have two constructs with the same semantic, i.e. two equal procedures P and Q (normal and inline) will exhibit the same behaviour in the entire program.

  Also, please keep in mind, everyone, that in the context of dynamically loadable (and discardable) modules you really don't want to inline a procedure that you've imported from another module. Because if that other module happens to change the procedure afterwards, you'll have the old copy in your code.


More information about the Oberon mailing list