Path: csiph.com!x330-a1.tempe.blueboxinc.net!aioe.org!texta.sil.at!newscore.univie.ac.at!aconews-feed.univie.ac.at!aconews.univie.ac.at!not-for-mail Newsgroups: comp.lang.java.programmer From: Andreas Leitgeb Subject: Re: boolean to int : was char to decimal References: <92ea64F3avU1@mid.individual.net> Reply-To: avl@logic.at User-Agent: slrn/pre0.9.9-111 (Linux) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: Date: 09 May 2011 23:54:10 GMT Lines: 11 NNTP-Posting-Host: gamma.logic.tuwien.ac.at X-Trace: 1304985250 tunews.univie.ac.at 60386 128.130.175.3 X-Complaints-To: abuse@tuwien.ac.at Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3882 Michael Wojcik wrote: > It's unlikely a Java implementation will benefit detectably from > anything other than the straightforward cascading-if-else design. > Certainly that would be the one to start with, and only investigate > alternatives if performance is a problem and profiling indicates this > is a useful target for optimization. The more those poor-man's bitsets have to be passed around or stored "en masse", rather than just being assembled and used (as in the switch example), the more it will pay.