<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hmm... it might be possible to add such a rule to SwaLint:<div><span style="font-size: 10pt"><a href="https://github.com/HPI-SWA-Teaching/SwaLint">https://github.com/HPI-SWA-Teaching/SwaLint</a></span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Best,</span></div><div><span style="font-size: 13.3333px">Marcel</span></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 10.09.2021 14:28:57 schrieb Levente Uzonyi <leves@caesar.elte.hu>:</p><div style='font-family:Arial,Helvetica,sans-serif'>On Fri, 10 Sep 2021, Marcel Taeumel wrote:<br><br>> A simple compiler warning in the Transcript might work. Like we have for Undeclared and shadowed variables ... maybe simple blacklist of "iconic" selectors such as #ifNotNilDo: ...<br><br>That would be a good start but I was thinking something more about a <br>linter-like tool for deprecated/undeclared/undefined stuff. :)<br><br><br>Levente<br><br></div></blockquote>
</div></body>