Woops, my bad again. I gotta stop responding to threads without really understanding what I'm talking about. I think I just noticed that both have flush() methods and I assumed that was to a String (which is wrong in the case of the decoder). I'll stop talking now.
On Thu, Sep 25, 2008 at 10:42 AM, Peter Farland <[EMAIL PROTECTED]> wrote: > Just curious, where'd folks see the decoder docs talk about a toString()? > Base64Decoder's primary use is to decode to a ByteArray so it has a > toByteArray() method. If you wanted to construct a String from this > ByteArray you'd need to know the charset encoding used in the bytes. > > Pete > >> -----Original Message----- >> From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On >> Behalf Of Doug McCune >> Sent: Thursday, September 25, 2008 1:29 PM >> To: flexcoders@yahoogroups.com >> Subject: Re: [flexcoders] Re: Base64Encoder / Base64Decoder >> >> I assume the bug here is that the toString() method was supposed to be >> implemented the same way in Base64Decoder as it is in Base64Encoder, >> which would then make the docs at least make sense. But it looks like >> that method simply got left out of the decoder class. Add it in just >> like in the encoder and things aren't as confusing (although I'd argue >> that using the toString() method to retrieve the result is an >> inherently confusing way to use the classes). >> >> Doug >> > >
