<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> My only guess is that POSIX wanted to allow for (POSIX) shells that sniff the &#39;#!&#39; line and exec something else for you, since POSIX doesn&#39;t require execl() to honor &#39;#!&#39; (although it can). POSIX requires execl() to pass things that are not &#39;valid executable objects&#39; to the POSIX sh, although I&#39;m sure POSIX also allows a &#39;#!&#39; shell script to be a valid executable object (since that was and is traditional Unix behavior for some Unixes).</p>
Reply