8346773: Fix unmatched brackets in some misc files
Reviewed-by: kbarrett, alanb, rriggs, dholmes, erikj, liach
This commit is contained in:
parent
9393897817
commit
f1d85ab3e6
@ -245,7 +245,7 @@ compare C string contents. There are also case-insensitive versions
|
|||||||
<p>All GoogleTest asserts print compared expressions and their values,
|
<p>All GoogleTest asserts print compared expressions and their values,
|
||||||
so there is no need to have them in error messages. Asserts print only
|
so there is no need to have them in error messages. Asserts print only
|
||||||
compared values, they do not print any of interim variables, e.g.
|
compared values, they do not print any of interim variables, e.g.
|
||||||
<code>ASSERT_TRUE((val1 == val2 && isFail(foo(8)) || i == 18)</code>
|
<code>ASSERT_TRUE((val1 == val2 && isFail(foo(8))) || i == 18)</code>
|
||||||
prints only one value. If you use some complex predicates, please
|
prints only one value. If you use some complex predicates, please
|
||||||
consider <code>EXPECT_PRED*</code> or <code>EXPECT_FORMAT_PRED</code>
|
consider <code>EXPECT_PRED*</code> or <code>EXPECT_FORMAT_PRED</code>
|
||||||
assertions family, they check that a predicate returns true/success and
|
assertions family, they check that a predicate returns true/success and
|
||||||
|
@ -172,7 +172,7 @@ Provide informative, but not too verbose error messages.
|
|||||||
All GoogleTest asserts print compared expressions and their values, so
|
All GoogleTest asserts print compared expressions and their values, so
|
||||||
there is no need to have them in error messages. Asserts print only
|
there is no need to have them in error messages. Asserts print only
|
||||||
compared values, they do not print any of interim variables, e.g.
|
compared values, they do not print any of interim variables, e.g.
|
||||||
`ASSERT_TRUE((val1 == val2 && isFail(foo(8)) || i == 18)` prints only
|
`ASSERT_TRUE((val1 == val2 && isFail(foo(8))) || i == 18)` prints only
|
||||||
one value. If you use some complex predicates, please consider
|
one value. If you use some complex predicates, please consider
|
||||||
`EXPECT_PRED*` or `EXPECT_FORMAT_PRED` assertions family, they check that
|
`EXPECT_PRED*` or `EXPECT_FORMAT_PRED` assertions family, they check that
|
||||||
a predicate returns true/success and print out all parameters values.
|
a predicate returns true/success and print out all parameters values.
|
||||||
|
@ -46,10 +46,10 @@
|
|||||||
$ jfr print dump.jfr
|
$ jfr print dump.jfr
|
||||||
|
|
||||||
Programmatic access:
|
Programmatic access:
|
||||||
try (var rf = new RecordingFile(Path.of("dump.jfr)) {
|
try (var rf = new RecordingFile(Path.of("dump.jfr"))) {
|
||||||
while (rf.hasMoreEvents()) {
|
while (rf.hasMoreEvents()) {
|
||||||
RecordedEvent e = rf.readEvent();
|
RecordedEvent e = rf.readEvent();
|
||||||
System.out.println(e.getName() + " " + e.getDuration()));
|
System.out.println(e.getName() + " " + e.getDuration());
|
||||||
}
|
}
|
||||||
};
|
};
|
||||||
!-->
|
!-->
|
||||||
|
@ -1218,7 +1218,7 @@ jvmtiEnv *jvmti;
|
|||||||
<li><i>Timed wait?</i>
|
<li><i>Timed wait?</i>
|
||||||
<ul>
|
<ul>
|
||||||
<li>Indefinite (<datalink
|
<li>Indefinite (<datalink
|
||||||
id="JVMTI_THREAD_STATE_WAITING_INDEFINITELY"><code>JVMTI_THREAD_STATE_WAITING_INDEFINITELY</code></datalink></li>
|
id="JVMTI_THREAD_STATE_WAITING_INDEFINITELY"><code>JVMTI_THREAD_STATE_WAITING_INDEFINITELY</code></datalink>)</li>
|
||||||
<li>Timed (<datalink
|
<li>Timed (<datalink
|
||||||
id="JVMTI_THREAD_STATE_WAITING_WITH_TIMEOUT"><code>JVMTI_THREAD_STATE_WAITING_WITH_TIMEOUT</code></datalink>)</li>
|
id="JVMTI_THREAD_STATE_WAITING_WITH_TIMEOUT"><code>JVMTI_THREAD_STATE_WAITING_WITH_TIMEOUT</code></datalink>)</li>
|
||||||
</ul>
|
</ul>
|
||||||
|
@ -1311,7 +1311,7 @@ These `java` options control the runtime behavior of the Java HotSpot VM.
|
|||||||
`-XX:+PreserveFramePointer`
|
`-XX:+PreserveFramePointer`
|
||||||
: Selects between using the RBP register as a general purpose register
|
: Selects between using the RBP register as a general purpose register
|
||||||
(`-XX:-PreserveFramePointer`) and using the RBP register to hold the frame
|
(`-XX:-PreserveFramePointer`) and using the RBP register to hold the frame
|
||||||
pointer of the currently executing method (`-XX:+PreserveFramePointer` . If
|
pointer of the currently executing method (`-XX:+PreserveFramePointer`). If
|
||||||
the frame pointer is available, then external profiling tools (for example,
|
the frame pointer is available, then external profiling tools (for example,
|
||||||
Linux perf) can construct more accurate stack traces.
|
Linux perf) can construct more accurate stack traces.
|
||||||
|
|
||||||
|
@ -662,7 +662,7 @@ perform.
|
|||||||
|
|
||||||
- {`-noprompt`}: Do not prompt
|
- {`-noprompt`}: Do not prompt
|
||||||
|
|
||||||
- {`-addprovider` *name* \[`-providerarg` *arg*\]: Add security provider
|
- {`-addprovider` *name* \[`-providerarg` *arg*\]}: Add security provider
|
||||||
by name (such as SunPKCS11) with an optional configure argument.
|
by name (such as SunPKCS11) with an optional configure argument.
|
||||||
|
|
||||||
- {`-providerclass` *class* \[`-providerarg` *arg*\]}: Add security
|
- {`-providerclass` *class* \[`-providerarg` *arg*\]}: Add security
|
||||||
@ -1617,7 +1617,7 @@ name information, the keystore password, and the private key password.
|
|||||||
The rest of the examples assume that you responded to the prompts with values
|
The rest of the examples assume that you responded to the prompts with values
|
||||||
equal to those specified in the first `-genkeypair` command. For example, a
|
equal to those specified in the first `-genkeypair` command. For example, a
|
||||||
distinguished name of
|
distinguished name of
|
||||||
`cn=`*myname*`, ou=`*mygroup*`, o=`*mycompany*`, c=`*mycountry*).
|
`cn=`*myname*`, ou=`*mygroup*`, o=`*mycompany*`, c=`*mycountry*.
|
||||||
|
|
||||||
## Requesting a Signed Certificate from a CA
|
## Requesting a Signed Certificate from a CA
|
||||||
|
|
||||||
@ -1914,7 +1914,7 @@ Keystore implementation
|
|||||||
The `keytool` command works on any file-based keystore implementation. It
|
The `keytool` command works on any file-based keystore implementation. It
|
||||||
treats the keystore location that is passed to it at the command line as a
|
treats the keystore location that is passed to it at the command line as a
|
||||||
file name and converts it to a `FileInputStream`, from which it loads the
|
file name and converts it to a `FileInputStream`, from which it loads the
|
||||||
keystore information.)The `jarsigner` commands can read a keystore from any
|
keystore information. The `jarsigner` commands can read a keystore from any
|
||||||
location that can be specified with a URL.
|
location that can be specified with a URL.
|
||||||
|
|
||||||
For `keytool` and `jarsigner`, you can specify a keystore type at the
|
For `keytool` and `jarsigner`, you can specify a keystore type at the
|
||||||
|
@ -1667,7 +1667,7 @@ internal and subject to change at any time.
|
|||||||
public static int m() {
|
public static int m() {
|
||||||
try {
|
try {
|
||||||
throw new NullPointerException();
|
throw new NullPointerException();
|
||||||
} catch (NullPointerException(); {
|
} catch (NullPointerException e) {
|
||||||
System.err.println("Caught NullPointerException.");
|
System.err.println("Caught NullPointerException.");
|
||||||
return 1;
|
return 1;
|
||||||
} finally {
|
} finally {
|
||||||
|
Loading…
x
Reference in New Issue
Block a user