From: Rob Pike <r@golang.org>
Date: Thu, 2 Jun 2011 14:09:42 +0000 (+1000)
Subject: template: explain that fields must be exported.
X-Git-Tag: weekly.2011-06-02~15
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=9995d216eb7442d8ec9b6f4c32f29b8289aa7dff;p=gostls13.git

template: explain that fields must be exported.
Fixes #1792.

R=golang-dev, dsymonds
CC=golang-dev
https://golang.org/cl/4548083
---

diff --git a/src/pkg/template/template.go b/src/pkg/template/template.go
index 1011190044..f481cbd1ee 100644
--- a/src/pkg/template/template.go
+++ b/src/pkg/template/template.go
@@ -17,12 +17,15 @@
 	Data items may be values or pointers; the interface hides the
 	indirection.
 
-	In the following, 'field' is one of several things, according to the data.
+	In the following, 'Field' is one of several things, according to the data.
 
-		- The name of a field of a struct (result = data.field),
-		- The value stored in a map under that key (result = data[field]), or
+		- The name of a field of a struct (result = data.Field),
+		- The value stored in a map under that key (result = data["Field"]), or
 		- The result of invoking a niladic single-valued method with that name
-		  (result = data.field())
+		  (result = data.Field())
+
+	If Field is a struct field or method name, it must be an exported
+	(capitalized) name.
 
 	Major constructs ({} are the default delimiters for template actions;
 	[] are the notation in this comment for optional elements):