From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 2/2] Cygwin: remove ENOSHARE and ECASECLASH from _sys_errlist[]
Date: Tue, 27 Feb 2024 15:59:51 +0100 [thread overview]
Message-ID: <Zd3457LfikTibhEm@calimero.vinschen.de> (raw)
In-Reply-To: <ede12d4d-3401-5d68-cfd1-f3aafa6a3394@t-online.de>
Hi Christian,
On Feb 27 13:18, Christian Franke wrote:
> From f495fb0e7c2bd3a42f16f81af18c64ffaba9a860 Mon Sep 17 00:00:00 2001
> From: Christian Franke <christian.franke@t-online.de>
> Date: Tue, 27 Feb 2024 13:05:36 +0100
> Subject: [PATCH 2/2] Cygwin: remove ENOSHARE and ECASECLASH from
> _sys_errlist[]
>
> These errno values are no longer used by Cygwin. Also add a
> static_assert check for _sys_errlist[] size.
>
> Signed-off-by: Christian Franke <christian.franke@t-online.de>
> ---
> winsup/cygwin/errno.cc | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/winsup/cygwin/errno.cc b/winsup/cygwin/errno.cc
> index 7d58e62ec..d8c057e51 100644
> --- a/winsup/cygwin/errno.cc
> +++ b/winsup/cygwin/errno.cc
> @@ -167,8 +167,8 @@ const char *_sys_errlist[] =
> /* ESTALE 133 */ "Stale NFS file handle",
> /* ENOTSUP 134 */ "Not supported",
> /* ENOMEDIUM 135 */ "No medium found",
> -/* ENOSHARE 136 */ "No such host or network path",
> -/* ECASECLASH 137 */ "Filename exists with different case",
> + NULL, /* Was ENOSHARE 136, no longer used. */
> + NULL, /* Was ECASECLASH 137, no longer used. */
In terms of politenness, wouldn't it be better to define them as
empty strings? This may be one crash less in already existing
binaries...
Corinna
next prev parent reply other threads:[~2024-02-27 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 12:16 [PATCH 1/2] Cygwin: add compile warning if ENOSHARE or ECASECLASH is used Christian Franke
2024-02-27 12:18 ` [PATCH 2/2] Cygwin: remove ENOSHARE and ECASECLASH from _sys_errlist[] Christian Franke
2024-02-27 14:59 ` Corinna Vinschen [this message]
2024-02-27 16:26 ` Christian Franke
2024-02-28 9:01 ` Corinna Vinschen
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=Zd3457LfikTibhEm@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).