<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Are you sure about this?<div><br></div><div>Both pm3 and cm3 load type structures from object files on initialization. Type data is in UNTRACED REF ARRAY… structures, for both of them.</div><div><br></div><div>Difference is in algorithm being incremental, "multi-pass" in cm3 and single-pass in pm3/SRC. Also, for garbage collection, there is a check to see if number of modules (meaning more globals areas) has grown, and rebuilding of globals list in case it is.</div><div> </div><div>There is nothing static in type structure of Modula-3.</div><div><br><div><div>On Jun 7, 2012, at 6:36 PM, Mika Nystrom wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Because of the restrictions of SRC and P M3, types are statically<br>allocated at compile time and all their subtyping relationships are known<br>at that time. There is simply a static array of the types.</span></blockquote></div><br></div></body></html>