[tor-commits] [tor/master] Explain config_line_find() behavior on duplicates.

nickm at torproject.org nickm at torproject.org
Thu Apr 6 15:51:27 UTC 2017


commit 5567a80caad0586b5d15db388339be4d276de136
Author: Nick Mathewson <nickm at torproject.org>
Date:   Thu Apr 6 08:53:26 2017 -0400

    Explain config_line_find() behavior on duplicates.
---
 src/common/confline.c | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/src/common/confline.c b/src/common/confline.c
index 6ec3b61..36f4c87 100644
--- a/src/common/confline.c
+++ b/src/common/confline.c
@@ -30,9 +30,11 @@ config_line_append(config_line_t **lst,
   (*lst) = newline;
 }
 
-/** Return the line in <b>lines</b> whose key is exactly <b>key</b>, or NULL
- * if no such key exists. For handling commandline-only options only; other
- * options should be looked up in the appropriate data structure. */
+/** Return the first line in <b>lines</b> whose key is exactly <b>key</b>, or
+ * NULL if no such key exists.
+ *
+ * (In options parsing, this is for handling commandline-only options only;
+ * other options should be looked up in the appropriate data structure.) */
 const config_line_t *
 config_line_find(const config_line_t *lines,
                  const char *key)





More information about the tor-commits mailing list