2020-06-28 16:26:19 +0100, Stephane Chazelas: [...] > See below for comments (mostly minor) on the XBD [Definitions] section. [...]
Following up with the next section (XBD 4 General concepts): > 2724 4.8 Filenames > 2725 Uppercase and lowercase letters shall retain their unique > identities between conforming > 2726 implementations. ??? Is that the definition of "Filenames"? > 2878 4.15 Process ID Reuse > 2879 A process group ID shall not be reused by the system until > the process group lifetime ends. > 2880 A process ID shall not be reused by the system until the > process lifetime ends. In addition, if > 2881 there exists a process group whose process group ID is > equal to that process ID, the process ID > 2882 shall not be reused by the system until the process group > lifetime ends. A process that is not a > 2883 system process shall not have a process ID of 1. What's a "system process"? It doesn't seem to be defined. > 3007 4.22 Utility > 3008 A utility program shall be either an executable file, such as > might be produced by a compiler or > 3009 linker system from computer source code, or a file of shell > source code, directly interpreted by > 3010 the shell. The program may have been produced by the user, > provided by the system > 3011 implementor, or acquired from an independent distributor. > 3012 The system may implement certain utilities as shell functions > (see XCU Section 2.9.5, on page > 3013 2302) or built-in utilities, but only an application that is > aware of the command search order (as > 3014 described in XCU Section 2.9.1.4, on page 2293) or of > performance characteristics can discern > 3015 differences between the behavior of such a function or built-in > utility and that of an executable > 3016 file. > Note that "Utility" is already defined (differently) in XBD 3.389. > > > 3017 4.23 Variable Assignment > 3018 In the shell command language, a word consisting of the > following parts: > 3019 varname=value How about assignments in awk, bc, env, make...?
