aboutsummaryrefslogtreecommitdiffstats
path: root/doc/dieshdiedie.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2025-04-28 08:43:53 +0000
committerLaurent Bercot <ska@appnovation.com>2025-04-28 08:43:53 +0000
commitff3a5ecf6f6bf9bb87682272f3eb800329572833 (patch)
treeeb3c4a810eca139fce134a40abc517be7198e78f /doc/dieshdiedie.html
parent7365249a1460289f0a047e12a0575ef326df194b (diff)
downloadexecline-ff3a5ecf6f6bf9bb87682272f3eb800329572833.tar.gz
Latest batch of fixes
Signed-off-by: Laurent Bercot <ska@appnovation.com>
Diffstat (limited to 'doc/dieshdiedie.html')
-rw-r--r--doc/dieshdiedie.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/dieshdiedie.html b/doc/dieshdiedie.html
index 383bcea..a84df31 100644
--- a/doc/dieshdiedie.html
+++ b/doc/dieshdiedie.html
@@ -34,7 +34,7 @@ on the subject</a>, section 5.)
But shells parse all the time. Worse, the <em>essence</em>
of the shell is parsing: the parser and the runner are intimately
interleaved and cannot be clearly separated, thanks to the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html">specification</a>.
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html">specification</a>.
The shell performs several kinds of expansions, automatic filename
globbing, and automatic word splitting, in an unintuitive order,
requiring users to memorize numerous arbitrary quoting rules in
@@ -143,7 +143,7 @@ can be configured to follow the slashpackage convention.
I originally wanted a shell that could be used on an embedded system.
Even the <tt>ash</tt> shell seemed big, so I thought of writing my
own. Hence I had a look at the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html">sh
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html">sh
specification</a>... and ran away screaming.
This specification
is <em>insane</em>. It goes against every good programming
@@ -155,7 +155,7 @@ to wannabe <tt>sh</tt> implementors.
POSIX cannot really be blamed for that: it only normalizes existing, historical
behaviour. One can argue whether it is a good idea to normalize atrocious
behaviour for historical reasons, as is the case with the infamous
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/gets.html">gets</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/functions/gets.html">gets</a>
function, but this is the way it is.
</p>