Re: RFR: 8305748: Clarify reentrant behavior of close() in FileInputStream, FileOutputStream, and RandomAccessFile [v3]

2023-05-09 Thread Brian Burkhalter
On Tue, 9 May 2023 22:10:22 GMT, Archie Cobbs wrote: > pingbot Thanks for the reminder. Too late to sponsor today so tomorrow. - PR Comment: https://git.openjdk.org/jdk/pull/13379#issuecomment-1541124772

Re: RFR: 8305748: Clarify reentrant behavior of close() in FileInputStream, FileOutputStream, and RandomAccessFile [v3]

2023-05-09 Thread Archie Cobbs
On Fri, 7 Apr 2023 18:24:42 GMT, Archie Cobbs wrote: >> IO stream classes like `FileOutputStream` can have assocated NIO channels. >> >> When `close()` is invoked on one of these classes, it in turn invokes >> `close()` on the associated channel (if any). But when the associated >> channel's

Re: RFR: 8305748: Clarify reentrant behavior of close() in FileInputStream, FileOutputStream, and RandomAccessFile [v3]

2023-04-10 Thread Brian Burkhalter
On Fri, 7 Apr 2023 18:24:42 GMT, Archie L. Cobbs wrote: >> IO stream classes like `FileOutputStream` can have assocated NIO channels. >> >> When `close()` is invoked on one of these classes, it in turn invokes >> `close()` on the associated channel (if any). But when the associated >>

Re: RFR: 8305748: Clarify reentrant behavior of close() in FileInputStream, FileOutputStream, and RandomAccessFile [v3]

2023-04-10 Thread Alan Bateman
On Fri, 7 Apr 2023 18:24:42 GMT, Archie L. Cobbs wrote: >> IO stream classes like `FileOutputStream` can have assocated NIO channels. >> >> When `close()` is invoked on one of these classes, it in turn invokes >> `close()` on the associated channel (if any). But when the associated >>

Re: RFR: 8305748: Clarify reentrant behavior of close() in FileInputStream, FileOutputStream, and RandomAccessFile [v3]

2023-04-07 Thread Archie L . Cobbs
> IO stream classes like `FileOutputStream` can have assocated NIO channels. > > When `close()` is invoked on one of these classes, it in turn invokes > `close()` on the associated channel (if any). But when the associated > channel's `close()` method is invoked, it in turn invokes `close()` on