diff options
| author | Daniel Dunbar <daniel@zuster.org> | 2009-11-22 22:07:50 +0000 |
|---|---|---|
| committer | Daniel Dunbar <daniel@zuster.org> | 2009-11-22 22:07:50 +0000 |
| commit | 964ac012017451ff24c33e6b749ec3223e1d291a (patch) | |
| tree | 578f11358b72553646d3997046834e7afe53eb74 /docs/CommandGuide/FileCheck.pod | |
| parent | a2f20b20a8dc7f053599840557405554a0848aec (diff) | |
Allow '_' in FileCheck variable names, it is nice to have at least one
separate character.
- Chris, OK?
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@89626 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/CommandGuide/FileCheck.pod')
| -rw-r--r-- | docs/CommandGuide/FileCheck.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/CommandGuide/FileCheck.pod b/docs/CommandGuide/FileCheck.pod index d3f640d64d..32516ad87b 100644 --- a/docs/CommandGuide/FileCheck.pod +++ b/docs/CommandGuide/FileCheck.pod @@ -224,7 +224,7 @@ The first check line matches a regex (<tt>%[a-z]+</tt>) and captures it into the variables "REGISTER". The second line verifies that whatever is in REGISTER occurs later in the file after an "andw". FileCheck variable references are always contained in <tt>[[ ]]</tt> pairs, are named, and their names can be -formed with the regex "<tt>[a-zA-Z][a-zA-Z0-9]*</tt>". If a colon follows the +formed with the regex "<tt>[a-zA-Z_][a-zA-Z0-9_]*</tt>". If a colon follows the name, then it is a definition of the variable, if not, it is a use. FileCheck variables can be defined multiple times, and uses always get the |