It is available in 1.4.2 indeed and that will have to do. The thing is that replaceAll uses regex and not regular string matching.
I'm thinking I'll end up dropping the replacing altogether. This was just for pruning the output that I am parsing as I go, but I can just not prune it and it'll be fine anyway. The trade-off between doing a regex search and having to search through some more characters is probably balanced, and regex would introduce some more issues in the end. On Thu, Jun 25, 2009 at 1:42 PM, Kathey Marsden <[email protected] > wrote: > Tiago Espinha wrote: > >> >> Finally, for some background, the overload is the >> String.replace(CharSequence, CharSequence);. On 1.4.2 there is only a >> replace method in Strings that takes two chars and it doesn't allow us to >> replace whole chunks of a string, so that's why I got the error. If I have >> to make it 1.4.2-compatible I am also open to suggestions on replacing >> chunks of a string, in this case with an empty string (so in essence, >> removing whole pieces of a string a string). >> >> I think replaceAll is available on 1.4.2. Will that work for you? > >
