From b2e6bc0ea2b2d2b90f6a159a23a4e676b1f302e4 Mon Sep 17 00:00:00 2001
From: Stef Walter <stef@thewalter.net>
Date: Tue, 16 Jul 2013 17:18:02 +0200
Subject: iter: Document guarantees for filter matches argumet

The matches argument is always initialized to CK_TRUE when a filter
is called, and it's up to filters to set it to CK_FALSE. Filters
don't need to set to CK_TRUE.

https://bugzilla.redhat.com/show_bug.cgi?id=985009
---
 p11-kit/iter.c | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'p11-kit')

diff --git a/p11-kit/iter.c b/p11-kit/iter.c
index 9c22ee0..a59944a 100644
--- a/p11-kit/iter.c
+++ b/p11-kit/iter.c
@@ -220,6 +220,10 @@ p11_kit_iter_set_session_flags (P11KitIter *iter,
  * indicates through it's <literal>matches</literal> argument that
  * the object should not match, then that object will not be iterated
  * as far as p11_kit_iter_next() is concerned.
+ *
+ * The callbacks will be called with the <literal>matches</literal>
+ * set to <literal>CK_TRUE</literal> and it's up to filters to change
+ * it to <literal>CK_FALSE</literal> when necessary.
  */
 void
 p11_kit_iter_add_callback (P11KitIter *iter,
-- 
cgit v1.1