A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1603 ====================================================================== Reported By: calestyo Assigned To: ====================================================================== Project: Issue 8 drafts Issue ID: 1603 Category: Base Definitions and Headers Type: Enhancement Request Severity: Editorial Priority: normal Status: New Name: Christoph Anton Mitterer Organization: User Reference: Section: 4.14 Pathname Resolution Page Number: 94 Line Number: 2850 ff Final Accepted Text: ====================================================================== Date Submitted: 2022-08-30 23:34 UTC Last Modified: 2022-09-01 08:23 UTC ====================================================================== Summary: minor error in the pathname resolution ======================================================================
---------------------------------------------------------------------- (0005952) geoffclare (manager) - 2022-09-01 08:23 https://austingroupbugs.net/view.php?id=1603#c5952 ---------------------------------------------------------------------- On the mailing list Lawrence Velázquez asked "Do lines 2857 through 2877 not address this sufficiently?" and Oğuz replied "They do". Whilst I agree that the requirements are clear when those lines are taken into account, I think some minor wording changes would be helpful. I suggest: On page 94 line 2839 change:<blockquote>Each filename in the pathname is located in the directory specified by its predecessor (for example, in the pathname fragment <b>a/b</b>, file <b>b</b> is located in directory <b>a</b>).</blockquote>to:<blockquote>Each filename in the pathname is located in the directory specified by its predecessor (for example, in the pathname fragment <b>a/b</b>, file <b>b</b> is located in the directory specified by <b>a</b>).</blockquote> On page 94 line 2851 change:<blockquote>unless the last pathname component before the trailing <slash> characters names an existing directory or a directory entry that is to be created for a directory immediately after the pathname is resolved.</blockquote>to:<blockquote>unless the last pathname component before the trailing <slash> characters resolves (with symbolic links followed - see below) to an existing directory or a directory entry that is to be created for a directory immediately after the pathname is resolved.</blockquote> I have not included any change for line 2875 - I believe "the directory containing the symbolic link" is fine. If this directory was arrived at via a symbolic link, it makes no difference as it is the directory itself that the text is referring to. Issue History Date Modified Username Field Change ====================================================================== 2022-08-30 23:34 calestyo New Issue 2022-08-30 23:34 calestyo Name => Christoph Anton Mitterer 2022-08-30 23:34 calestyo Section => 4.14 Pathname Resolution 2022-08-30 23:34 calestyo Page Number => 94 2022-08-30 23:34 calestyo Line Number => 2850 ff 2022-08-30 23:50 calestyo Note Added: 0005950 2022-08-30 23:51 calestyo Note Edited: 0005950 2022-08-30 23:51 calestyo Note Added: 0005951 2022-09-01 08:23 geoffclare Note Added: 0005952 ======================================================================
