 #- you can also omit the  "var err error" line if you change the = to := on the
 #- next line, since at least one of the LHS operands is being declared.
 #-
+#**
+#** author: Tom Roeder
+#** email: tmroeder@google.com
+#** date 2014-07-12T09:11:00-0700
+#**
+#-- Well, the standard Go idiom likes compound error if statements, but it's
+#-- true that it also prefers compound inits like &Signer{ec} over new(Signer)
+#-- whenever possible. I think I like your suggestion better in this case.
+#--
+#-- And thanks for catching the err declaration question. It's true in this
+#-- I tend towards declaring my errors to avoid error shadowing, which is
+#-- explicitly supported in Go and sometimes trips me up. I'll change it here.
+#--
  
 -// instantiateKey creates a Keyczar key of a given type, with an optional path,
 -// a name, and an optional crypter for encrypting or decrypting the key. It

#- programs, since programs don't suddenly change languages. On the other hand,
#- there might be keys that are shared between programs.
#-
 
-// CrypterPath returns the path to the encryption key, if any.
-func (k *Keys) CrypterPath() string {

#- Is zeroBytes() just wishful thinking in a garbage collected language? I
#- suppose we might as well make the effort.
#-
#**
#** author: Tom Roeder
#** email: tmroeder@google.com
#** date 2014-07-12T09:11:00-0700
#**
#-- Yeah, more or less. The "right" way in a garbage collected language would be
#-- to have unsafe code that manages the memory explicitly and doesn't let the
#-- garbage collector touch it. But of course, that's wrong in other ways...
#-- So, this is best effort.
#--
 }
diff --git a/go/src/cloudproxy/tao/keys.pb.go b/go/src/cloudproxy/tao/keys.pb.go
index c750ca8..9cfef8d 100644
