parent
cb0960a91e
commit
a5b99dce5d
4 changed files with 26 additions and 13 deletions
@ -1,17 +1,15 @@ |
||||
## String escape character update |
||||
## String escape character sequence update |
||||
|
||||
The strings (both single-quoted and triple-quoted) in meson has been taught the |
||||
same set of escape sequences as in Python. It is therefore now possible to use |
||||
arbitrary bytes in strings, like for example NUL (`\0`) and other ASCII control |
||||
characters. See the chapter about *Strings* in *Syntax* for more details. |
||||
Single-quoted strings in meson have been taught the same set of escape |
||||
sequences as in Python. It is therefore now possible to use arbitrary bytes in |
||||
strings, like for example `NUL` (`\0`) and other ASCII control characters. See |
||||
the chapter about [*Strings* in *Syntax*](Syntax.md#strings) for more |
||||
details. |
||||
|
||||
Potential backwards compatibility issue: Any valid escape sequence according to |
||||
the new rules will be interpreted as an escape sequence instead of the literal |
||||
characters. Previously only single-quote strings supported escape sequences and |
||||
the supported sequences were `\'`, `\\` and `\n`. |
||||
characters. Previously only the following escape sequences were supported in |
||||
single-quote strings: `\'`, `\\` and `\n`. |
||||
|
||||
The most likely breakage is usage of backslash-n in triple-quoted strings. It |
||||
is now written in the same way as in single-quoted strings: `\\n` instead of |
||||
`\n`. In general it is now recommended to escape any usage of backslash. |
||||
However, backslash-c (`\c`), for example, is still backslash-c because it isn't |
||||
a valid escape sequence. |
||||
Note that the behaviour of triple-quoted (multiline) strings has not changed. |
||||
They behave like raw strings and do not support any escape sequences. |
||||
|
Loading…
Reference in new issue