| Rev | Author | # | Line |
|---|---|---|---|
| 1 | JohnMcPherson | 1 | [POSIXLY_CORRECT] is an EnvironmentVariable that some programs use to follow strict [POSIX] standards behaviour, where that isn't the default. |
| 2 | |||
| 3 | Probably the most well-known example of this is that [POSIX] states that filesystem blocks are 512 bytes per block, so the [GNU] fileutils such as df(1) and GNU tar(1) use 512 if the variable [POSIXLY_CORRECT] is set, and 1024 bytes per block by default. (See [Democracy Triumphs in Disk Units | http://groups.google.com/groups?selm=9108281809.AA03552%40mole.gnu.ai.mit.edu]) | ||
| 4 | |||
| 5 | Many of the GNU tools comply with [POSIX] by default, except for where the author thinks the [POSIX] standard is wrong or dumb. <tt>:)</tt> For the same reason, some programs treat an variable named [POSIX_ME_HARDER] as an acceptable alias for [POSIXLY_CORRECT]. | ||
| 6 | |||
| 7 | Some programs that behave differently if [POSIXLY_CORRECT] is set: | ||
| 6 | AristotlePagaltzis | 8 | |
| 1 | JohnMcPherson | 9 | * bash(1) |
| 10 | * df(1) | ||
| 11 | * patch(1) | ||
| 6 | AristotlePagaltzis | 12 | * true(1), false(1) and yes(1) |
| 13 | |||
| 14 | From the NEWS file for true(1)/false(1): | ||
| 15 | > false and true now ignore <tt>--help</tt> and <tt>--version</tt> when [POSIXLY_CORRECT] is set. | ||
| 16 | |||
| 17 | yes(1) prints these options as output strings rather than ignoring them. | ||
| 18 | |||
| 19 | * any program using getopt(3), since the function stops processing options after the first non-option if [POSIXLY_CORRECT] is set |
lib/blame.php:177: Warning: Invalid argument supplied for foreach()