RPCS3/llvm
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm.git synced 2024-11-30 23:21:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: Improve typographical correctness.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@167998 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Sean Silva 2012-11-14 23:15:51 +00:00
parent d5f4b4ca0d
commit 791ebec45b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/TestingGuide.rst
View File

@ -479,7 +479,7 @@ The CHECK: and CHECK-NOT: directives both take a pattern to match. For
most uses of FileCheck, fixed string matching is perfectly sufficient.
For some things, a more flexible form of matching is desired. To support
this, FileCheck allows you to specify regular expressions in matching
strings, surrounded by double braces: **{{yourregex}}**. Because we want
strings, surrounded by double braces: ``{{yourregex}}``. Because we want
to use fixed string matching for a majority of what we do, FileCheck has
been designed to support mixing and matching fixed string matching with
regular expressions. This allows you to write things like this:
@ -495,7 +495,7 @@ Because regular expressions are enclosed with double braces, they are
visually distinct, and you don't need to use escape characters within
the double braces like you would in C. In the rare case that you want to
match double braces explicitly from the input, you can use something
ugly like **{{[{][{]}}** as your pattern.
ugly like ``{{[{][{]}}`` as your pattern.
FileCheck Variables
^^^^^^^^^^^^^^^^^^^