Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed1.swip.net!newsfeed2.funet.fi!newsfeeds.funet.fi!feeder1.news.elisa.fi!uutiset.elisa.fi!7564ea0f!not-for-mail From: Jukka Lahtinen Newsgroups: comp.lang.java.programmer Subject: Re: Help with methods, classes and parameters Organization: N/A References: <53d993b9$0$299$14726298@news.sunsite.dk> X-no-archive: yes Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:In7Wd1Vgs9gZ5AaHGTnI/u+uJ9E= MIME-Version: 1.0 Content-Type: text/plain Lines: 17 Date: Fri, 01 Aug 2014 12:02:06 +0300 NNTP-Posting-Host: 91.155.88.191 X-Complaints-To: newsmaster@saunalahti.com X-Trace: uutiset.elisa.fi 1406883726 91.155.88.191 (Fri, 01 Aug 2014 12:02:06 EEST) NNTP-Posting-Date: Fri, 01 Aug 2014 12:02:06 EEST Xref: csiph.com comp.lang.java.programmer:29480 markspace writes: > switch (optionInt) { > case 0: > return; > break; > I left in the break because when you edit a program, sometimes you forget > and change things, and the break helps prevent an unexpected fall through > when you make a change. It doesn't hurt anything to leave it in even > though the break is extraneous. However, I suspect it may cause a warning about unreachable code and even prevent compilation with some IDE settings. -- Jukka Lahtinen