[9] RFR of 8042377: BufferedWriter and FilteredOutputStream.close throw IAE if flush and close throw equal exceptions

Jason Mehrens jason_mehrens at hotmail.com
Thu Jun 25 00:40:06 UTC 2015


If the other I/O classes are using it then it should be safe here then.  Just wanted make sure it wasn't creating a new issue.


Thanks,


Jason

----------------------------------------
> From: brian.burkhalter at oracle.com
> Subject: Re: [9] RFR of 8042377: BufferedWriter and FilteredOutputStream.close throw IAE if flush and close throw equal exceptions
> Date: Wed, 24 Jun 2015 13:28:17 -0700
> To: core-libs-dev at openjdk.java.net
>
> I should however note that equivalent usage is already present in the close() methods of FileInputStream, FileOutputStream, and RandomAccessFile which are also in java.io. Perhaps the problem you allude to would be more pertinent to java.lang classes?
>
> Brian
>
> On Jun 24, 2015, at 1:21 PM, Brian Burkhalter <brian.burkhalter at oracle.com> wrote:
>
>> Jason,
>>
>> Thanks for pointing this out. I am not sure of the answer. Let’s see what the experts have to say.
>>
>> Thanks,
>>
>> Brian
>>
>> On Jun 24, 2015, at 1:03 PM, Jason Mehrens <jason_mehrens at hotmail.com> wrote:
>>
>>> Not sure on this but, isn't it a little risky to import AtomicBoolean into such low level class? I vaguely remember there was an issue with using AtomicXXX in java.lang.Thread. Not sure if this case suffers the same fate.
> 		 	   		  


More information about the core-libs-dev mailing list