[GnuPG] gpgme_set_locale on global context fails ?
Marcus Brinkmann
marcus.brinkmann at ruhr-uni-bochum.de
Sat Jul 28 01:18:29 CEST 2012
Hi,
thanks, it turns out my checking-spree went over the line with that one.
;)
Reverted in 434735f71e6969248651ac01c6bd6f6789a6305d.
Marcus
On 07/27/2012 10:40 PM, W. Trevor King wrote:
> On Fri, Jul 27, 2012 at 08:53:18PM +0200, Leo Gaspard wrote:
>> I'm learning GPGME, and just tried to use gpgme_set_locale. However,
>> it looks like it doesn't work on the global context, only on a
>> normal one.
>
> That would be because the definition is currently:
>
> gpgme_error_t
> gpgme_set_locale (gpgme_ctx_t ctx, int category, const char *value)
> {
> …
> if (!ctx)
> return TRACE_ERR (gpg_error (GPG_ERR_INV_VALUE));
>
> It looks like Marcus just got into the zone with:
>
> commit b34add3fe438a693e236a835135bd11b4e177daa
> Author: Marcus Brinkmann <marcus.brinkmann at ruhr-uni-bochum.de>
> Date: Thu May 26 16:01:26 2011 +0200
>
> Check context pointers for null pointer on entry points.
>
> But it looks like gpgme_set_locale actually does handle the !ctx case
> well.
>
> Cheers,
> Trevor
>
>
>
> _______________________________________________
> Gnupg-devel mailing list
> Gnupg-devel at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-devel
>
More information about the Gnupg-devel
mailing list