Reply to thread

Message: [QUOTE="John C. Bollinger, post: 646931"] It depends on how you define "the job". I have trouble believing that one invocation of the constructor you are using takes a human-discernible amount of time, so you must be doing many such decodings. That being the case, it is unclear how you are certain that your problem is in that constructor, as opposed to anywhere else in the data processing procedure. Have you profiled the application? It is not worth your time or mine to speculate on how to speed it up without knowing precisely where all the cycles are going. If you *have* profiled it then we can guide you better based on the full results, whether or not it turns out to be the String constructor that is eating all the time. [/QUOTE]