Ok, I looked more closely and dicovered one difference between
Classpath's and libgcj's PipedInputStream. Classpath says this:
/* ...
* *****What is this method really supposed to do *********
*/
protected synchronized void
receive(int byte_received) throws IOException
I interpreted this method as being the interface between
PipedOutputStream and PipedInputStream. The docs aren't that clear, I
admit, but this seems like a reasonable interpretation.
I didn't test it :-(. I'll try to get around to doing that.
In libgcj, I implemented a receive(byte[],...) -- basically what the
Classpath implementation calls write(). This seemed like a natural
extension to get better performance.
I think making receive() visible was a mistake on Sun's part.
Tom
