<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Lazy... you've got a bloody cheek. Well I guess there's no point
in me contributing anything more if that's how you honestly view
me. I wasn't aware of the ISO that dictated that a case block
shouldn't just fall through until today, and C/C++ and Basic never
threw similar errors or warnings, so I didn't know this was a
thing.</p>
<p>Good day.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 18/05/2019 22:56, Ralf Quint wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4aa53961-bbcc-e579-2c8b-7ff9ef2f071a@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 5/18/2019 4:30 AM, J. Gareth
Moreton wrote:<br>
</div>
<blockquote type="cite"
cite="mid:03f089b6-76b5-72c7-157f-6539aa6c33d8@moreton-family.com">Hi
everyone, <br>
<br>
So it looks like this new warning has appeared as part of the
data flow analysis of -O4. The thing is, I personally have a
problem with this being a warning, because there's nothing
inherently wrong with not covering every case branch or omitting
an else block (especially if one isn't needed). Adding "else ;"
everywhere seems to just cause bloat. <br>
<br>
Still, code style aside, can I suggest the warning be downgraded
into a hint? Warnings should indicate the possibility of
unstable code due to uninitialised values, for example, and DFA
should be able to detect that anyway as a separate warning (e.g.
if a case block doesn't initialise an output value in all of its
branches). </blockquote>
<p>Sorry, but you seem to suffer from the "lazy programmer
syndrome". A warning is correct, as a case of unhandled <b><i>case</i></b>
statement can indeed lead to unexpected side effects. While
there could be cases where you might want to react with the <i><b>case</b></i>
statement to only certain conditions (and can safely assume that
all other conditions don't do ill effects), there is also the
case where an unknown/unexpected condition is passed and that
can have dire consequences, and should be properly acted upon,
by the <i><b>else</b></i> clause within the case statement...</p>
<p>Ralf<br>
</p>
<br>
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top: 1px solid #D3D4DE;">
<tbody>
<tr>
<td style="width: 55px; padding-top: 13px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon"
target="_blank" moz-do-not-send="true"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt="" style="width: 46px; height: 29px;"
moz-do-not-send="true" width="46" height="29"></a></td>
<td style="width: 470px; padding-top: 12px; color:
#41424e; font-size: 13px; font-family: Arial, Helvetica,
sans-serif; line-height: 18px;">Virus-free. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link"
target="_blank" style="color: #4453ea;"
moz-do-not-send="true">www.avast.com</a> </td>
</tr>
</tbody>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
height="1" moz-do-not-send="true"> </a></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
fpc-devel maillist - <a class="moz-txt-link-abbreviated" href="mailto:fpc-devel@lists.freepascal.org">fpc-devel@lists.freepascal.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel">http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel</a>
</pre>
</blockquote>
</body>
</html>