Re: What replaces StringBufferInputStream

From:

"Mike Schilling" <mscottschilling@hotmail.com>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 30 Aug 2006 12:41:44 GMT

Message-ID:

<cIfJg.4410$yO7.4354@newssvr14.news.prodigy.com>

"Chris Uppal" <chris.uppal@metagnostic.REMOVE-THIS.org> wrote in message
news:44f550df$0$637$bed64819@news.gradwell.net...

Oliver Wong wrote:

Setting an explicit encoding (to me) implies that that's the actual
encoding you want to use, as opposed to you having just chosen an
encoding
randomly because you didn't know which one was appropriate.

Fair point.

With luck (i.e. I haven't bothered to check) the US-ASCII decoder will
signal
an error if it is fed bytes outside the [0, 127] range. If so then
setting
that would be one way to be explicit about the assumption (almost
certainly
correct) that I think Patricia's making.

Not quite so much luck.

import java.io.*;

public class BadAscii
{
    public static void main(String[] args) throws Exception
    {
        byte arr[] = { (byte)0x40, (byte)0x80};

        ByteArrayInputStream bais = new ByteArrayInputStream(arr);
        InputStreamReader isr = new InputStreamReader(bais, "US-ASCII");
        while (true)
        {
            int r = isr.read();
            if (r < 0)
                break;
            System.out.println(
                (char)r + "(" + Integer.toHexString(r) + ")");
        }
    }
}

results in

% java -cp . BadAscii
@(40)
?(fffd)

So, no exception, but the FFFD is a clear indication that there's been a
decoding error.