This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
PR/19801: Change file names in cppinternals.texi
- From: Paolo Bonzini <paolo dot bonzini at lu dot unisi dot ch>
- To: GCC Patches <gcc-patches at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Tue, 08 Feb 2005 10:24:52 +0100
- Subject: PR/19801: Change file names in cppinternals.texi
Fairly obvious. Ok for mainline?
Paolo
2005-02-08 Paolo Bonzini <bonzini@gnu.org>
* doc/cppinternals.texi (Conventions, Lexer, Files): Adjust
filenames that changed when libcpp was moved to the toplevel.
Index: cppinternals.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/cppinternals.texi,v
retrieving revision 1.20
diff -u -F^@node -r1.20 cppinternals.texi
--- cppinternals.texi 6 Feb 2005 20:20:56 -0000 1.20
+++ cppinternals.texi 8 Feb 2005 09:24:31 -0000
@@ -112,7 +112,7 @@ @node Conventions
The convention is that functions and types that are exposed to multiple
files internally are prefixed with @samp{_cpp_}, and are to be found in
-the file @file{cpphash.h}. Functions and types exposed to external
+the file @file{internal.h}. Functions and types exposed to external
clients are in @file{cpplib.h}, and prefixed with @samp{cpp_}. For
historical reasons this is no longer quite true, but we should strive to
stick to it.
@@ -131,7 +131,7 @@ @node Lexer
@cindex escaped newlines
@section Overview
-The lexer is contained in the file @file{cpplex.c}. It is a hand-coded
+The lexer is contained in the file @file{lex.c}. It is a hand-coded
lexer, and not implemented as a state machine. It can understand C, C++
and Objective-C source code, and has been extended to allow reasonably
successful preprocessing of assembly language. The lexer does not make
@@ -996,7 +996,7 @@ @node Files
@cindex files
Fairly obviously, the file handling code of cpplib resides in the file
-@file{cppfiles.c}. It takes care of the details of file searching,
+@file{files.c}. It takes care of the details of file searching,
opening, reading and caching, for both the main source file and all the
headers it recursively includes.