> ---------------------------------------------------------------------- > (0004073) kre (reporter) - 2018-08-06 15:06 > http://austingroupbugs.net/view.php?id=1123#c4073 > ---------------------------------------------------------------------- > Thanks for note 4072. > > Upon reflection, the proposed wording for the final paragraph is all > wrong, and more complex than it needs to be. Instead of what I suggested > for that final paragraph, instead please consider > > If the result of an expansion from steps 1, 2, or 3 above results > in a completely empty field, that field shall be deleted. However > if step 4 produces an empty field, that field shall be retained.
For step 1 this would conflict with 2.5.2 which says that empty fields resulting from expanding @ and * _may_ be discarded. Your suggestion would require them to be discarded instead of it being optional. > But while considering that, I also realised that line 74998 > > The order of word expansion shall be as follows: > > also needs work (apart from the missing plural of expansion). > > So, also please consider replacing that line (74998) with: > > While not all of the following word expansions are always > performed, those that are performed occur in the following order: > > or something like it. Eg: case patterns do not do filename expansion, > or field splitting, and subject to the resolution of another issue, > probably (hopefully) (once again) will not do quote removal either. > PSn expansions don't do them all either. This is already covered by the second sentence of 2.6, "Not all expansions are performed on every word, as explained in the following sections." -- Geoff Clare <[email protected]> The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
