On Mon, 12 May 2025 10:16:33 GMT, David Beaumont <d...@openjdk.org> wrote:

>> Adding read-only support to ZipFileSystem.
>> 
>> The new `accessMode` environment property allows for readOnly and readWrite 
>> values, and ensures that the requested mode is consistent with what's 
>> returned.
>> 
>> This involved a little refactoring to ensure that "read only" state was set 
>> initially and only unset at the end of initialization if appropriate.
>> 
>> By making 2 methods return values (rather than silently set non-final fields 
>> as a side effect) it's now clear in what order fields are initialized and 
>> which are final (sadly there are still non-final fields, but only a split of 
>> this class into two types can fix that, since determining multi-jar support 
>> requires reading the file system).
>
> David Beaumont has updated the pull request incrementally with one additional 
> commit since the last revision:
> 
>   Fix comment based on current behaviour.

src/jdk.zipfs/share/classes/jdk/nio/zipfs/ZipFileSystem.java line 160:

> 158: 
> 159:         // Parses the file system permission from an environmental 
> parameter. While
> 160:         // the FileSystemAccessMode is private, we don't need to check 
> if it was

The second sentence perhaps is a leftover? I don't see any 
`FileSystemAccessMode` type. I think it would be better to remove that second 
sentence altogether. The rest of the comment looks good and clearly states what 
this method does.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/25178#discussion_r2086897450

Reply via email to