A NOTE has been added to this issue. ====================================================================== https://www.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-08-30 23:50 UTC ====================================================================== Summary: minor error in the pathname resolution ======================================================================
---------------------------------------------------------------------- (0005950) calestyo (reporter) - 2022-08-30 23:50 https://www.austingroupbugs.net/view.php?id=1603#c5950 ---------------------------------------------------------------------- I think there are further such cases: - line 2840, "in the pathname fragment a/b, file b is located in directory a", a might not be a directory, but also a symlink pointing to such - Cases where I think it's really just directory: - always when it says "directory entry" - line 2839, "Each filename in the pathname is located in the directory specified by its predecessor", because of the "specified" which a symlink also does - line 2875, "If the resulting pathname does not begin with a <slash>, the predecessor of the first filename of the pathname is taken to be the directory containing the symbolic link."... the predecessor could be a symlink, so shouldn't it somehow say that it's taken to be the target of such, if it is one? Unsure: - line 2842, "root directory of the process" ... I'd assume the process root dir is always resolved already to a true directory?, just as the current working directory in line 2845? ... Similar in line 2888 So better some expert check these :-) (thx) 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 ======================================================================
