On Monday 19 Mar 2012 22:37:05 Marco Schulze wrote: > On 19-03-2012 18:56, Marco Schulze wrote: > > On 19-03-2012 16:42, Matthew Toseland wrote: > >> PrintWriter (System.err) busy-loops. :( It is probably possible to > >> get the underlying OutputStream though. > > Will take a look at it. > From what I found after a quick googling, full disk errors do throw an > IOException, but is silently ignored by various OutputStream subclasses > (except for write(byte[])). No mention of any busy-loop, however.
I am speaking from experience. write() is supposed to either succeed or throw. PrintWriter busy-loops on disk full when stderr is redirected to a file. Feel free to test it, it may be that it doesn't happen with modern JVMs. But it's unacceptable. Usually when you see this sort of convoluted stuff, there is a reason for it. Any solution that "simplifies" it and makes it more "elegant" must address all the problems that caused the complexity in the first place! If it doesn't the various patches will just be re-added, wasting everyone's time.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
