From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] linux: make getcwd(3) fail if it cannot obtain an absolute path [BZ #22679]
Date: Sun, 07 Jan 2018 17:07:00 -0000 [thread overview]
Message-ID: <20180107170736.GB15678@altlinux.org> (raw)
In-Reply-To: <CAKCAbMiLkpkO6+suhU1e0DqO-_DMrvg1G6GhGO3WojyfsYGm9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Sun, Jan 07, 2018 at 11:21:19AM -0500, Zack Weinberg wrote:
> On Sun, Jan 7, 2018 at 11:07 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> > On Jan 07 2018, Zack Weinberg <zackw@panix.com> wrote:
> >
> >> http://pubs.opengroup.org/onlinepubs/9699919799/functions/getcwd.html
> >> does not license getcwd to fail with ENOENT.
> >
> > That's not true. It doesn't specify any condition for ENOENT, thus we
> > can use it for our purpose.
>
> I thought the ERRORS sections were meant to be exhaustive - no other
> errors are allowed.
Just the otherwise: "Implementations may support additional errors not
included in this list, may generate errors included in this list under
circumstances other than those described here, or may contain extensions
or limitations that prevent some errors from occurring."
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-01-07 17:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 3:05 Dmitry V. Levin
2018-01-07 8:23 ` Andreas Schwab
2018-01-07 11:33 ` Dmitry V. Levin
2018-01-07 12:20 ` Andreas Schwab
2018-01-07 12:36 ` Dmitry V. Levin
2018-01-07 12:41 ` [PATCH v2] " Dmitry V. Levin
2018-01-07 13:10 ` Florian Weimer
2018-01-07 13:39 ` [PATCH v3] " Dmitry V. Levin
2018-01-08 15:07 ` Dmitry V. Levin
2018-01-11 22:03 ` [PATCH v4] " Dmitry V. Levin
2018-01-11 23:44 ` Florian Weimer
2018-01-12 0:11 ` Dmitry V. Levin
2018-01-12 12:56 ` Florian Weimer
2018-01-07 15:53 ` [PATCH] " Zack Weinberg
2018-01-07 16:07 ` Andreas Schwab
2018-01-07 16:21 ` Zack Weinberg
2018-01-07 17:07 ` Dmitry V. Levin [this message]
2018-01-07 20:04 ` Zack Weinberg
2018-01-07 16:24 ` Dmitry V. Levin
2018-02-05 19:03 ` Florian Weimer
2018-02-05 19:18 ` Andreas Schwab
2018-02-05 20:03 ` Florian Weimer
2018-02-06 0:10 ` Dmitry V. Levin
2018-02-06 16:57 ` Florian Weimer
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=20180107170736.GB15678@altlinux.org \
--to=ldv@altlinux.org \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.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).