<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: inherit;">Lars</div><div style="direction: inherit;"><br></div><div style="direction: inherit;">Dynamic vs static is perhaps not the best distinction of modules vs objects.</div><div style="direction: inherit;">I try to make an analogon.</div><div style="direction: inherit;">- Modules can be seen as car manufacturer.</div><div style="direction: inherit;">- Objects are the cars.</div><div style="direction: inherit;"><br></div>Car manufacturers are static in the sense that the define a distinct set of cars in their portfolio. But they are also dynamic because they can change their car portfolio. Or even in another sense dynamic, they can go bancrupt and do not produce cars anymore. Or another car manufacturer appears on the market.</div><div id="AppleMailSignature" style="direction: inherit;"><br></div><div id="AppleMailSignature" style="direction: inherit;">But also cars have both flavours. The car us dynamic in the sense that it gets produced, is used and perhaps after 300000 km get shredded. On the other side it is kind of static as it is as it is; once it is produced it has either 3 doors or 5 doors.</div><div id="AppleMailSignature" style="direction: inherit;"><br></div><div id="AppleMailSignature">br</div><div id="AppleMailSignature">Jörg</div><div><br>Am 23.09.2016 um 03:18 schrieb Lars <<a href="mailto:noreply@z505.com">noreply@z505.com</a>>:<br><br></div><blockquote type="cite"><div><span>On Mon, September 5, 2016 4:01 pm, Jörg Straube wrote:</span><br><blockquote type="cite"><span>Another aspect of modules.</span><br></blockquote><blockquote type="cite"><span>You tried to make the boundary of modules as static vs OOP as dynamic.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>You are right: Modules are static in the sense that they deckare the</span><br></blockquote><blockquote type="cite"><span>TYPEs the abstracted assets have.</span><br></blockquote><span></span><br><span>Somewhere there is an article from N. Wirth about this and he describes a</span><br><span>module very similar to an object that cannot be dynamically loaded, but is</span><br><span>statically loaded at design time. In fact actually it's interesting with</span><br><span>oberon systems though where you can load modules into the system, I</span><br><span>think.. and unload them... so then the distinction becomes even less clear</span><br><span>as they sort of can be dynamically loaded (not created so much).</span><br><span></span><br><span>It was either Wirth (pretty sure) or another famous Oberon programmer who</span><br><span>wrote the article. Maybe I'll find it but I'm too lazy to search for now.</span><br><span>--</span><br><span><a href="mailto:Oberon@lists.inf.ethz.ch">Oberon@lists.inf.ethz.ch</a> mailing list for ETH Oberon and related systems</span><br><span><a href="https://lists.inf.ethz.ch/mailman/listinfo/oberon">https://lists.inf.ethz.ch/mailman/listinfo/oberon</a></span><br></div></blockquote></body></html>