<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
I moved this submission to the treated inbox because we seem to agree that caseOf does not improve readability here.<div><br></div><div>In general, I would try to preserve the original meaning, which would have been that "<span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">self error: 'implementation error'." be the otherwise-clause.</span><br><div><div><br></div><div>Best,</div><div>Marcel</div></div></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 15.08.2019 18:59:06 schrieb tim Rowledge <tim@rowledge.org>:</p><div style="font-family:Arial,Helvetica,sans-serif"><br><br>> On 2019-08-15, at 2:10 AM, Thiede, Christoph <christoph.thiede@student.hpi.uni-potsdam.de> wrote:<br>> <br>> Of course, excessive use of #caseOf: might indicate the lack of an inheritance tree, but I don't think this is specific to #caseOf:, the same smell can be written with many conditionals as well.<br><br>It is a long understood truism that there is no language in which the poor programmer cannot write FORTRAN.<br><br>I've long ago lost count of the number of times I have seen stuff like<br><br>(thing isKindOf: Weeble) ifTrue:["do something daft"].<br>(thing isKindOf: Blobby) ifFalse: ["do related ridiculous thing that could be factored properly"].<br>thing doodah caseOf: .... etc etc<br><br>I used to find it disheartening. Now I just find it tedious and occasionally profitable as I get paid to make it right.<br><br>tim<br>--<br>tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim<br>Oxymorons: Government organization<br><br><br><br></christoph.thiede@student.hpi.uni-potsdam.de></div></blockquote>
</div></body>