From d1445f8d81fe014e5457cd978116f13e9cf6a419 Mon Sep 17 00:00:00 2001 From: Andreas Bauer Date: Tue, 29 Oct 2002 22:39:49 +0000 Subject: [PATCH] * doc/c-tree.texi (Tree overview): Fix typos. From-SVN: r58640 --- gcc/ChangeLog | 4 ++++ gcc/doc/c-tree.texi | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index edd8a7eb247..6250ccd56dc 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2002-10-28 Andreas Bauer + + * doc/c-tree.texi (Tree overview): Fix typos. + 2002-10-29 Phil Edwards * Makefile.in (gnucompare*): Only record bad comparisons diff --git a/gcc/doc/c-tree.texi b/gcc/doc/c-tree.texi index 0b9f4d69d75..8f5a5bb74d2 100644 --- a/gcc/doc/c-tree.texi +++ b/gcc/doc/c-tree.texi @@ -84,8 +84,8 @@ we will refer to trees in ordinary type, rather than in @code{this font}, except when talking about the actual C type @code{tree}. You can tell what kind of node a particular tree is by using the -@code{TREE_CODE} macro. Many, many macros take a trees as input and -return trees as output. However, most macros require a certain kinds of +@code{TREE_CODE} macro. Many, many macros take trees as input and +return trees as output. However, most macros require a certain kind of tree node as input. In other words, there is a type-system for trees, but it is not reflected in the C type-system.