aboutsummaryrefslogtreecommitdiff
path: root/docs/InternalsManual.html
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2011-10-12 16:37:45 +0000
committerDouglas Gregor <dgregor@apple.com>2011-10-12 16:37:45 +0000
commit4a8dfb511e8f84b2e38b7a86d8ddf05ac1e1a41b (patch)
tree51429fab5effd4a81368c423996e314d702e1bad /docs/InternalsManual.html
parentd41679d6881d2b424d8b3600fc774308087735a7 (diff)
Introduce BalancedDelimiterTracker, to better track open/close
delimiter pairs and detect when we exceed the implementation limit for nesting depth, from Aaron Ballman! git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@141782 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/InternalsManual.html')
-rw-r--r--docs/InternalsManual.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/InternalsManual.html b/docs/InternalsManual.html
index 2829dbdd75..da83d89acc 100644
--- a/docs/InternalsManual.html
+++ b/docs/InternalsManual.html
@@ -1810,7 +1810,7 @@ focus on expressions, but statements are similar.</p>
<li>Write tests for all of the "bad" parsing cases, to make sure
your recovery is good. If you have matched delimiters (e.g.,
parentheses, square brackets, etc.), use
- <tt>Parser::MatchRHSPunctuation</tt> to give nice diagnostics when
+ <tt>Parser::BalancedDelimiterTracker</tt> to give nice diagnostics when
things go wrong.</li>
</ul>
</li>