From: storm@cua.dk (Kim F. Storm)
Cc: "emacs-devel" <emacs-devel@gnu.org>
Subject: Re: Updates to configure for make-network-process
Date: 20 Mar 2002 00:35:31 +0100 [thread overview]
Message-ID: <5x1yegyvuk.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <m34rjcgp3x.fsf@nyaumo.btinternet.com>
Jason Rumney <jasonr@gnu.org> writes:
> storm@cua.dk (Kim F. Storm) writes:
>
> > How would you verify the features without defining them?
>
> Define them locally, and fix the problems before checking in. But I
> see it is already changed, so it might as well stay like that until
> someone gets time to implement wrappers for these functions on Windows.
>
> > Having them defined is not supposed to change anything
>
> Having them defined does change things. It is now necessary to link
> against a library that is not present on all versions of Windows,
> which previous code has made a lot of effort to accommodate. It is
> also necessary to specify extra link options to allow the library to
> co-exist with the overridden functions already present in Emacs.
I wasn't aware of this, and the feedback I got didn't indicate
any such problems.
I tried looking at the existing wrappers, and I think I could add the
missing functions -- but I have no way of testing it.
If I understand the code correctly, I have to define the wrappers in w32.c
and add the new functions to nt/inc/socket.h. I assume I can use e.g.
sys_connect as a skeleton for the new wrappers. Anything else I need
to be aware of?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-19 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-19 9:24 Updates to configure for make-network-process David Ponce
2002-03-19 19:22 ` Jason Rumney
2002-03-19 22:21 ` Kim F. Storm
2002-03-19 22:38 ` Jason Rumney
2002-03-19 23:35 ` Kim F. Storm [this message]
2002-03-20 0:13 ` Jason Rumney
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=5x1yegyvuk.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.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.