Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #31155
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: ensuring unreachability |
| Date | 2015-02-19 15:24 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <mc5go3$hul$1@dont-email.me> (permalink) |
| References | (4 earlier) <mc2577$4vj$1@dont-email.me> <lvh9uj9tal.fsf@saunalahti.fi> <mc2ab7$p6q$1@dont-email.me> <mc2d1a$4r1$1@dont-email.me> <mc59hi$sm5$1@Gaia.teknon.de> |
On 2/19/2015 1:20 PM, Volker Borchert wrote: > 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. > Mechanical code reviews are OK as a first pass, but I've seen them miss too many logic errors. I much prefer eyeballing by a different programmer. It's how I've run all the projects I've managed over the last 25 years. -- ================== Remove the "x" from my email address Jerry Stuckle jstucklex@attglobal.net ==================
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