From fd1cefda5892e57f9d2c9dd264e24a9f878346d0 Mon Sep 17 00:00:00 2001 From: Chong Yidong Date: Sat, 28 Nov 2009 21:09:00 +0000 Subject: * semantic.texi (Analyzer Internals): Rename from Analyzer. * sem-user.texi (Semantic mode user commands): Fix key syntax. Document semantic-complete-analyze-inline. (Semanticdb search debugging commands): Minor clarification. (Analyzer, Smart Completion, Smart Summary, Smart Jump) (Analyzer Debug) New nodes, adapted from the upstream Semantic user manual. --- doc/misc/semantic.texi | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'doc/misc/semantic.texi') diff --git a/doc/misc/semantic.texi b/doc/misc/semantic.texi index 064f1a6e3ae..b880f1a20fc 100644 --- a/doc/misc/semantic.texi +++ b/doc/misc/semantic.texi @@ -240,8 +240,8 @@ more about how @semantic{} works. @menu * Parser code :: Code used for the parsers * Tag handling :: Code used for manipulating tags -* Semanticdb internals :: Code used in the semantic database -* Analyzer :: Code used in the code analyzer +* Semanticdb Internals :: Code used in the semantic database +* Analyzer Internals :: Code used in the code analyzer * Tools :: Code used in user tools * Tests :: Code used for testing @end menu @@ -349,8 +349,8 @@ Capture documentation comments from near a tag. @end table -@node Semanticdb internals -@section Semanticdb internals +@node Semanticdb Internals +@section Semanticdb Internals @acronym{Semanticdb} complexity is certainly an issue. It is a rather hairy problem to try and solve. @@ -400,8 +400,8 @@ need to be flushed. References are in the form of include files. @end table -@node Analyzer -@section Analyzer +@node Analyzer Internals +@section Analyzer Internals The @semantic{} analyzer is a complex engine which has been broken down across several modules. When the @semantic{} analyzer fails, -- cgit v1.2.1