aboutsummaryrefslogtreecommitdiffstats
path: root/include/llvm
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2002-04-28 04:47:06 +0000
committerChris Lattner <sabre@nondot.org>2002-04-28 04:47:06 +0000
commit20ad298c748085c918600c0605ec64de291b344f (patch)
treef4e7d20a59289a37a62e052590e60ea9f47e7589 /include/llvm
parent356b79320b053b77562b47c076c753ab4c4d60d7 (diff)
downloadexternal_llvm-20ad298c748085c918600c0605ec64de291b344f.zip
external_llvm-20ad298c748085c918600c0605ec64de291b344f.tar.gz
external_llvm-20ad298c748085c918600c0605ec64de291b344f.tar.bz2
s/Method/Function
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@2348 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'include/llvm')
-rw-r--r--include/llvm/ValueHolder.h19
1 files changed, 9 insertions, 10 deletions
diff --git a/include/llvm/ValueHolder.h b/include/llvm/ValueHolder.h
index 6e251ff..af08212 100644
--- a/include/llvm/ValueHolder.h
+++ b/include/llvm/ValueHolder.h
@@ -1,11 +1,11 @@
//===-- llvm/ValueHolder.h - Class to hold multiple values -------*- C++ -*--=//
//
-// This defines a class that is used as a fancy Definition container. It is
-// special because it helps keep the symbol table of the container method up to
-// date with the goings on inside of it.
+// This defines a class that is used as a fancy Definition container. It is
+// special because it helps keep the symbol table of the container function up
+// to date with the goings on inside of it.
//
// This is used to represent things like the instructions of a basic block and
-// the arguments to a method.
+// the arguments to a function.
//
//===----------------------------------------------------------------------===//
@@ -17,11 +17,10 @@
// ValueSubClass - The type of objects that I hold
// ItemParentType - I call setParent() on all of my "ValueSubclass" items, and
// this is the value that I pass in.
-// SymTabType - This is the class type (which should be derived from
-// SymTabValue), whose symtab I insert my ValueSubClass items
-// into. Most of the time it is ItemParentType, but
-// Instructions have item parents of bb's but symtabtype's of
-// a Method
+// SymTabType - This is the class type, whose symtab I insert my
+// ValueSubClass items into. Most of the time it is
+// ItemParentType, but Instructions have item parents of BB's
+// but symtabtype's of a Function
//
template<class ValueSubclass, class ItemParentType, class SymTabType>
class ValueHolder {
@@ -42,7 +41,7 @@ public:
inline ~ValueHolder() {
// The caller should have called delete_all first...
assert(empty() && "ValueHolder contains definitions!");
- assert(Parent == 0 && "Should have been unlinked from method!");
+ assert(Parent == 0 && "Should have been unlinked from function!");
}
inline const SymTabType *getParent() const { return Parent; }