Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: ensuring unreachability Date: Wed, 18 Feb 2015 10:16:27 -0500 Organization: A noiseless patient Spider Lines: 35 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 18 Feb 2015 15:15:51 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="858a9d65d95f4ea4d355bd116aa2cdbf"; logging-data="25818"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/pJRouLsblGkWRiunYXEKz" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 In-Reply-To: Cancel-Lock: sha1:7xLlJ9lNQp60v38ZzdNiQbXliE8= Xref: csiph.com comp.lang.java.programmer:31146 On 2/18/2015 9:40 AM, Jukka Lahtinen wrote: > Eric Sosman writes: > >> Remember, the underlying purpose is to guard against a >> maintainer who might inadvertently introduce a fall-through. > > Why not just insert the break; for every case? > That's what it is for. The original code was oddly structured: case E1: if (...) { ...; return; } else if (...) { ...; throw ...; } else { ...; continue; } case E2: ... Inserting a `break' right before the E2 case would provoke a compile-time error because the statement would be unreachable. Andreas worries that someone might add a new alternative to the `if' ladder, one that doesn't `return' or `throw' or otherwise exit the `switch', thereby producing an unwanted fall-through into E2. I think the most straightforward way to accomplish this is to eliminate the final `else' and brackets, putting the `...; continue;' at the "top level" of the case. -- esosman@comcast-dot-net.invalid "Don't be afraid of work. Make work afraid of you." -- TLM