Re: PATCH: Improve POSIX conformance in dejagnu(1)
Jacob Bachmeyer <[email protected]>
| Newsgroups | gmane.comp.sysutils.dejagnu.general |
|---|---|
| Message-ID | <[email protected]> |
Ben Elliston wrote: > On Fri, Dec 28, 2018 at 06:46:47PM -0600, Jacob Bachmeyer wrote: > >> This patch removes the one use of semicolon in a sed(1) program in >> the dejagnu(1) multi-launcher. >> > Thanks. It's also just clearer! > > BTW, do you know about the --posix option to sed? > In this case that would be unlikely to help: POSIX explicitly allows using semicolon as a command separator as an extension. :-) (It also seems to be historical practice: configure itself uses this feature.) Also, various GNU programs have differing notions of what "POSIX mode" is. For example, GNU Awk seems (as far as I have looked so far) to actually be POSIX Awk if --posix is given, but bash is well-known for still offering GNU extensions even when "POSIX mode" is selected. Bash POSIX mode only guarantees that a script written to POSIX will run, not that scripts that run under "bash --posix" will actually also run under a POSIX shell. >-< -- Jacob