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: References: X-Trace: individual.net YpRMvCiSOXFEoMIl7qFQQgNrtVKcBSDY68f2y1a+9orx6uPpIU Cancel-Lock: sha1:TnOhW0Y3JkfyhqWmBJokN+nnUMU= Xref: csiph.com comp.lang.java.programmer:31154 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 "I'm a mechanic, not a doctor." Volker Borchert