Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #31142
| From | Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: ensuring unreachability |
| Date | 2015-02-18 00:40 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <slrnme7nt2.uoi.avl@login.logic.tuwien.ac.at> (permalink) |
| References | <slrnme63vm.uoi.avl@login.logic.tuwien.ac.at> <statement-20150217115740@ram.dialup.fu-berlin.de> <mc09k1$3se$1@dont-email.me> |
Eric Sosman <esosman@comcast-dot-net.invalid> wrote:
>> Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> writes:
>>> would recognize it as unreachable and barf. So, I'd like to have some
>>> kind of anti-statement, that's ok to be unreachable, but would make the
> It occurs to me that there is, sort of:
> final boolean once;
> switch (someEnumVar) {
> case E1:
> once = true;
> if (...) {
> ...; return;
> } else if (...) {
> ...; throw ...;
> } else {
> ...; continue; // enclosing loop
> }
> case E2:
> once = true; // compiler complains if fall-through possible
> ...
> case E3:
> once = true; // ditto
> ...
> }
> IMHO, this particular cure is a lot worse than the disease.
Despite your own judgement of it, this is awesome!
Thanks!
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
ensuring unreachability Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2015-02-17 09:54 +0000
Re: ensuring unreachability Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-02-17 08:23 -0500
Re: ensuring unreachability Leif Roar Moldskred <leifm@huldreskog.localdomain> - 2015-02-17 13:54 -0600
Re: ensuring unreachability Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-02-17 15:51 -0500
Re: ensuring unreachability Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2015-02-18 00:40 +0000
Re: ensuring unreachability Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-02-18 08:49 -0500
Re: ensuring unreachability Jukka Lahtinen <jtfjdehf@hotmail.com.invalid> - 2015-02-18 16:40 +0200
Re: ensuring unreachability Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-02-18 10:16 -0500
Re: ensuring unreachability Jerry Stuckle <jstucklex@attglobal.net> - 2015-02-18 11:02 -0500
Re: ensuring unreachability Robbie Brown <rob@example.com> - 2015-02-19 09:48 +0000
Re: ensuring unreachability Gene Wirchenko <genew@telus.net> - 2015-02-20 09:39 -0800
Re: ensuring unreachability Robbie Brown <rob@example.com> - 2015-02-19 09:50 +0000
Re: ensuring unreachability v_borchert@despammed.com (Volker Borchert) - 2015-02-19 18:20 +0000
Re: ensuring unreachability Jerry Stuckle <jstucklex@attglobal.net> - 2015-02-19 15:24 -0500
Re: ensuring unreachability Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2015-02-19 01:28 +0000
Re: ensuring unreachability Arne Vajhøj <arne@vajhoej.dk> - 2015-02-17 18:49 -0500
Re: ensuring unreachability Martin Gregorie <martin@address-in-sig.invalid> - 2015-02-18 00:59 +0000
csiph-web