[19069] in Kerberos_V5_Development
Re: Questions about iter check in profile_iterator()
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Jan 12 22:40:55 2015
Message-ID: <54B493B7.4020909@mit.edu>
Date: Mon, 12 Jan 2015 22:40:39 -0500
From: Greg Hudson <ghudson@mit.edu>
MIME-Version: 1.0
To: Neng Xue <neng.xue@oracle.com>, krbdev@mit.edu
In-Reply-To: <20150113011349.GA7054@oracle.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 01/12/2015 07:06 PM, Neng Xue wrote:
> So my question is that do we use the
> profile_iterator() in the wrong way or there should be an iter check in
> the profile_iterator()? Thanks.
The loop condition should be "state != NULL" rather than "code == 0".
profile_iterator_create returns 0 and sets *iter_p to NULL on the last
iteration.
On 01/12/2015 08:13 PM, Will Fiveash wrote:
> So in the profile_iterator call to profile_node_iterator() the
> &iter->idata arg is iter_p for profile_node_iterator? Seems odd to me.
I don't see what is odd about that. iter->idata holds the node iterator
state.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
