<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Subbu,<div><br></div><div>you cannot. :-) That's a good thing.</div><div><br></div><div>As you mentioned, you can document the specific role of a particular method to inform the programmer about side effects. Also, you can add tests that check for such "contracts" in the system. Well, for really dangerous stuff, there might be a hard-coded guard in compiler class. Yet, such guards can easily be overruled by custom compilers.</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 04.03.2019 02:16:38 schrieb K K Subbu <kksubbu.ml@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">All,<br><br><br>How does one enforce finality of methods in Squeak?<br><br>I noticed that methods like Object>>basicSize have instructions in <br>comments not to override these, but what if these methods do get <br>overridden/extended during compilation (perhaps by accident or oversight).<br><br>Can we use a dummy primitive in these methods to mark them as final?<br><br>Regards .. Subbu<br><br></div></blockquote>
</div></body>