<div dir="ltr"><div>Hi there,<br><br>> Maybe I am wrong and miss some point here. Someone could explain to me why there are no macros in Oberon?<br><br>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.<br>
The only difference is how they will be placed in the call site and this is the business of the code generator, and since the performance's result is platform dependent it shouldn't be left to the programmer how and when a procedure has to be inlined or not.<br>
<br>And remember: There should be one -- and preferably only one -- obvious way to do it.<br><br>--<br></div>Diego Sardina<br></div>