[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] GnuTLS support on Woe32

From: Juanma Barranquero
Subject: Re: [PATCH] GnuTLS support on Woe32
Date: Mon, 2 May 2011 18:20:56 +0200

On Wed, Apr 27, 2011 at 14:19, Juanma Barranquero <address@hidden> wrote:

> GnuTLS was one of the reasons that prompted me to change
> `image-library-alist' to `dynamic-library-alist', so yes, I plan to do
> it if nobody beats me to it.
> But I won't be able to spend time on that in at least a week or two,
> perhaps more, so there's ample time for someone to step in...

I'm working on this.

First question: what should the code do when the gnutls library cannot
be loaded at runtime? I mean, which is the single point that can
return a failure exit code, let's say, GNUTLS_EMACS_ERROR_NOT_LOADED
(== GNUTLS_E_APPLICATION_ERROR_MIN + 1), so the rest of the GnuTLS
code is disabled?

I'm thinking there will be a function init_gnutls_functions (), called
from syms_of_gnutls or Fgnutls_boot, which in addition to adjusting
the function pointers, sets a success/failure flag. And then, from the
elisp side, either that variable of a function gnutls-is-loaded-p
which the gnutls.el functions will have to consult.

Does that sound right? If so, can you take care of the gnutls.el side of things?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]