[Oberon] Life without local procedures
andreas_pirklbauer at yahoo.com
Fri Feb 23 14:53:31 CET 2018
> but for other objects as types, constants and procedures
> this is a bad idea since the cost (in runtime) is null.
PS: On a more general note: Just because something doesn’t
carry an implementation or runtime cost is a rather poor reason
for introducing (or in this case, retaining) a feature.
There are equally good reasons for the other way, e.g., to
make the handling of intermediate objects consistent (less
confusing to programmers, fewer rules to learn), to be able
to define a more uniform set of shadowing rules, etc.
It can be endlessly debated (and.. not really all that interesting)
More information about the Oberon