From: Daniel Colascione <dancol@dancol.org>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Re: BROKEN_NON_BLOCKING_CONNECT
Date: Fri, 27 Mar 2015 19:41:27 -0700 [thread overview]
Message-ID: <551614D7.9010900@dancol.org> (raw)
In-Reply-To: <55159A35.70907@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
On 03/27/2015 10:58 AM, Paul Eggert wrote:
> On 03/27/2015 02:59 AM, Eli Zaretskii wrote:
>> Are there any other platforms that might
>> need it and the related SELECT_CAN_DO_WRITE_MASK and
>> NON_BLOCKING_CONNECT? Or can these be deleted now?
> No platforms should need BROKEN_NON_BLOCKING_CONNECT or
> SELECT_CAN_DO_WRITE_MASK, so I removed them by applying the attached
> patch. Platforms that predate POSIX.1-2001 might need
> NON_BLOCKING_CONNECT, though, since that feature wasn't standardized by
> POSIX until POSIX.1-2001, so I left that part alone for now.
>
> This raises the topic of how far back in history Emacs should go, when
> trying to support older platforms. Currently Emacs is quite
> conservative and relies only on POSIX.1-1988 or later. I don't know of
> any currently-supported GNUish or Unixish platform that doesn't largely
> conform to POSIX.1-2001 or later, so as far as I know the Emacs code
> that runs only on hosts predating POSIX-2001 isn't being tested and
> quite possibly no longer works. So it would make sense for Emacs to
> start assuming POSIX.1-2001 or later
It'd be nice to assume UNICODE on Windows too. Windows 95 will be 20
years old in August.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-28 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 9:59 BROKEN_NON_BLOCKING_CONNECT Eli Zaretskii
2015-03-27 17:58 ` BROKEN_NON_BLOCKING_CONNECT Paul Eggert
2015-03-28 2:41 ` Daniel Colascione [this message]
2015-03-28 6:52 ` BROKEN_NON_BLOCKING_CONNECT Eli Zaretskii
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=551614D7.9010900@dancol.org \
--to=dancol@dancol.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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.