2023-05-03 11:06:20 +02:00
== Why is this an issue?
2020-06-30 12:48:07 +02:00
There is potential for confusion if an octal or hexadecimal escape sequence is immediately followed by other characters. Instead, such sequences should be terminated by either:
2020-06-30 14:49:38 +02:00
2020-06-30 12:48:07 +02:00
* The start of another escape sequence.
* The end of the string.
2023-05-03 11:06:20 +02:00
=== Noncompliant code example
2020-06-30 12:48:07 +02:00
2022-02-04 17:28:24 +01:00
[source,java]
2020-06-30 12:48:07 +02:00
----
String hasHex = "\x41g"; // Noncompliant
String hasOct = '\141t'; // Noncompliant
----
2023-05-03 11:06:20 +02:00
=== Compliant solution
2020-06-30 12:48:07 +02:00
2022-02-04 17:28:24 +01:00
[source,java]
2020-06-30 12:48:07 +02:00
----
String hasHex = "\x41" + "g"; // Compliant - terminated by end of literal
String hasOct = "\x41\x67"; // Compliant - terminated by another escape
----
2021-06-02 20:44:38 +02:00
2021-06-03 09:05:38 +02:00
ifdef::env-github,rspecator-view[]
2021-09-20 15:38:42 +02:00
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
2021-06-08 15:52:13 +02:00
'''
2021-06-02 20:44:38 +02:00
== Comments And Links
(visible only on this page)
include::comments-and-links.adoc[]
2021-06-03 09:05:38 +02:00
endif::env-github,rspecator-view[]