Groups > comp.lang.java.programmer > #31154

Re: ensuring unreachability

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	v_borchert@despammed.com (Volker Borchert)
Newsgroups	comp.lang.java.programmer
Subject	Re: ensuring unreachability
Date	19 Feb 2015 18:20:34 GMT
Organization	Private site at Eddersheim, Germany
Lines	16
Distribution	world
Message-ID	<mc59hi$sm5$1@Gaia.teknon.de> (permalink)
References	<slrnme63vm.uoi.avl@login.logic.tuwien.ac.at> <statement-20150217115740@ram.dialup.fu-berlin.de> <mc09k1$3se$1@dont-email.me> <slrnme7nt2.uoi.avl@login.logic.tuwien.ac.at> <mc2577$4vj$1@dont-email.me> <lvh9uj9tal.fsf@saunalahti.fi> <mc2ab7$p6q$1@dont-email.me> <mc2d1a$4r1$1@dont-email.me>
X-Trace	individual.net YpRMvCiSOXFEoMIl7qFQQgNrtVKcBSDY68f2y1a+9orx6uPpIU
Cancel-Lock	sha1:TnOhW0Y3JkfyhqWmBJokN+nnUMU=
Xref	csiph.com comp.lang.java.programmer:31154

Show key headers only | View raw

Jerry Stuckle wrote:

> You need to give the maintainer some credit, also.  A maintainer has to
> be familiar enough with code that he/she can make the necessary changes.
>  This means not only the syntax of the language, but the operation of
> the code he/she is changing, and what it can affect in other areas of
> the code.  And if he/she does make a change like the OP is concerned
> about, then a code review and/or testing should catch it.

Where the code review in this case can be done mechanically, e.g.
by findbugs, which would complain about the fallthru.

-- 

"I'm a doctor, not a mechanic." Dr Leonard McCoy <mccoy@ncc1701.starfleet.fed>
"I'm a mechanic, not a doctor." Volker Borchert  <v_borchert@despammed.com>

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