|
From: | Jonny Grant |
Subject: | Re: Bash handling of ENOENT on missing files and directories |
Date: | Mon, 11 Sep 2017 22:49:47 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 |
On 11/09/17 20:58, Bob Proulx wrote:
Jonny Grant wrote:Greg Wooledge wrote:The wording is taken directly from perror() and related library calls, as translated for your locale.Yes, it's a known limitation of POSIX that it uses a shared error code for both files and directors, ENOENT. Which without programmers handling and checking the stat() flags, means the error isn't completely clear in the case where a file or dir does exist.I don't see how POSIX is involved in this. Blaming POSIX is a complete non-sequitur here.
Why do you feel it isn't?
I imagine we have spoken already for longer about this, than it would have been to fix it.I see no bug to fix here. However I fear that trying to fix an imaginary one would introduce a bug here.
How can an easy update to clarify message "No such file or directory" introduce a bug?
Jonny
[Prev in Thread] | Current Thread | [Next in Thread] |