From d071845f64a7d3297f1ac62fd25b0a7c2886f736 Mon Sep 17 00:00:00 2001
From: Chris Lattner
Date: Wed, 17 Feb 2010 19:51:31 +0000
Subject: [PATCH] fix some out of date prose dating from the LLVMContext
changes.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@96500 91177308-0d34-0410-b5e6-96231b3b80d8
---
docs/tutorial/LangImpl3.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/tutorial/LangImpl3.html b/docs/tutorial/LangImpl3.html
index 39ec62852a8..47cf62ecad6 100644
--- a/docs/tutorial/LangImpl3.html
+++ b/docs/tutorial/LangImpl3.html
@@ -170,7 +170,7 @@ internally (APFloat has the capability of holding floating point
constants of Arbitrary Precision). This code basically just
creates and returns a ConstantFP. Note that in the LLVM IR
that constants are all uniqued together and shared. For this reason, the API
-uses "the Context.get..." idiom instead of "new foo(..)" or "foo::Create(..)".
+uses the "foo::get(...)" idiom instead of "new foo(..)" or "foo::Create(..)".
@@ -323,10 +323,10 @@ really talks about the external interface for a function (not the value computed
by an expression), it makes sense for it to return the LLVM Function it
corresponds to when codegen'd.
-The call to Context.get creates
+
The call to FunctionType::get creates
the FunctionType that should be used for a given Prototype. Since all
function arguments in Kaleidoscope are of type double, the first line creates
-a vector of "N" LLVM double types. It then uses the Context.get
+a vector of "N" LLVM double types. It then uses the Functiontype::get
method to create a function type that takes "N" doubles as arguments, returns
one double as a result, and that is not vararg (the false parameter indicates
this). Note that Types in LLVM are uniqued just like Constants are, so you