8370568: Refer to Thread.interrupted as "interrupted status" consistently #27972
+207
−207
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Throughout documentation and source code, the
Thread.interruptedflag is referred to as either "interrupted status" or "interrupt status". It might be good to be consistent.Historically, it seems to have initially been "interrupted status". This is how the flag is called in
java.lang.Threadand the "Java Concurrency in Practice" book. ("The Java Programming Language" calls it "interrupted state".) However, over the years "interrupt status" appeared in documentation and source code through networking and NIO classes.Progress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27972/head:pull/27972$ git checkout pull/27972Update a local copy of the PR:
$ git checkout pull/27972$ git pull https://git.openjdk.org/jdk.git pull/27972/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27972View PR using the GUI difftool:
$ git pr show -t 27972Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27972.diff