[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: On shishi_parse_name().
From: |
Mats Erik Andersson |
Subject: |
Re: On shishi_parse_name(). |
Date: |
Wed, 15 Aug 2012 20:07:19 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
onsdag den 15 augusti 2012 klockan 19:17 skrev Simon Josefsson detta:
> Mats Erik Andersson <address@hidden> writes:
>
> > The API call shishi_parse_name() is notable
> > on two more accounts:
> >
> > * The Shishi handle is part of the signature,
> > but it is never used,
>
> Yes, this was intentional so that if something from the handle will ever
> be needed in the future, we can use it.
>
> > so the expected call shishi_error() is reporting irrelevant text when
> > called after a failure in shishi_parse_name(). Can an error
> > condition in shishi_parse_name() be inserted into the handle's
> > context?
>
> I've added some shishi_error_printf, what do you think?
I was kind of wandering whether there exists an API call
that lets me register an error condition in the handle.
Intuitively I was hoping for a call like
shishi_register_error_state (handle, shishi_errno, err_msg);
which would raise, in the opaque Shishi handle, whatever
error semaphors there might be. Should shishi_parse_name()
be discontent with the given principal name, this would
provide a means for reporting an error exception.
Regards,
Mats