Hi Mat,

 >> +1.  Although we do have precedent for this in l_string_free, but that
>> is mostly how GLib API was done.
>
> Ok, I'll go with l_key_revoke_and_free(). It was l_string_free that sent
> me in the original add-a-flag direction, but that's also a function that
> has been a source of confusion.
>

Yeah, blame GLib for that.  The point of ell was to make it easy to port 
GLib based projects, so I'm not sure if changing l_string_free is better 
or worse.

I would personally vote for l_key_free and l_key_free_norevoke.

Regards,
-Denis