Yes - it needs to be int. Regardless, we need to focus on the things that are actually consuming run time, and this method isn't one of them (no matter how much it could be optimized).
Mike Marchywka-2 wrote: > > > > > does this have to be int vs char or byte? I think earlier I suggested > operating on byte[] instead of making a bunch of temp strings > but I don't know the context well enough to know if this makes sense. > Certainly demorgan can help but casts and calls are not free either. > > Also, maybe hotspot runtime has gotten better but I have found in > the past that look up tables can quickly become competititve > with bit operators ( if your param is byte instead of int, a > 256 entry table can tell you if the byte is a member of which classes). > > > -- View this message in context: http://old.nabble.com/performance-follow-up-tp28322800p28343789.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.itextpdf.com/book/ Check the site with examples before you ask questions: http://www.1t3xt.info/examples/ You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
