From: Juanma Barranquero <lekktu@gmail.com>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: gnutls on mingw64
Date: Fri, 29 Nov 2019 04:16:56 +0100 [thread overview]
Message-ID: <CAAeL0SQoUf_4z_No8=tHtk5oERj28ssqMJ3_ysT5AN3kgKskpw@mail.gmail.com> (raw)
In-Reply-To: <86v9r3op8n.fsf@stephe-leake.org>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Thu, Nov 28, 2019 at 10:08 PM Stephen Leake <
stephen_leake@stephe-leake.org> wrote:
> I'm also assuming that whoever wrote w32_delayed_load tested calling
> GetLastError, got an unhelpful message, and deleted it. It would be nice
> if there was a comment saying that.
"Whoever wrote w32_delayed_load" didn't do that, because the already
existing code
that loaded the image libraries didn't do it either. The whoever-dude just
added a
mechanism to allow the user to add new image libraries on their own, which
was
previously impossible because they were hard-coded (if such-and-such-v2
loads, then
good, else if such-and-such-v1 loads, then good too, else oh no!).
I'm not saying that the whoever-dude shouldn't have done what you suggest,
just
that he was fixing other issue and didn't even think of calling
GetLastError.
Bad, bad whoever-dude! ;-)
[-- Attachment #2: Type: text/html, Size: 1583 bytes --]
prev parent reply other threads:[~2019-11-29 3:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 12:34 gnutls on mingw64 Stephen Leake
2019-11-26 15:42 ` Richard Copley
2019-11-27 1:10 ` Stephen Leake
2019-11-27 8:56 ` Richard Copley
2019-11-27 9:58 ` Stephen Leake
2019-11-26 15:46 ` Eli Zaretskii
2019-11-27 10:00 ` Stephen Leake
2019-11-27 15:53 ` Eli Zaretskii
2019-11-28 18:00 ` Stephen Leake
2019-11-28 22:22 ` Richard Copley
2019-11-29 7:17 ` Eli Zaretskii
2019-11-29 8:32 ` Richard Copley
2019-11-29 10:24 ` Eli Zaretskii
2019-11-29 3:16 ` Juanma Barranquero [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAeL0SQoUf_4z_No8=tHtk5oERj28ssqMJ3_ysT5AN3kgKskpw@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.