From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] History of #! interpretation in Unix
Date: Sun, 16 Jan 2011 16:37:38 -0500 [thread overview]
Message-ID: <20110116213738.GG3374@mercury.ccil.org> (raw)
In-Reply-To: <20110116210812.GB26424@lisa.in-ulm.de>
Sven Mascheck scripsit:
> who (or what system) do you mean was the 2nd?
That was hypothetical.
Trying again: "It's unlikely that two different people chose #! as the
executable-script mark independently."
> With /bin/sh you actually meant any shell calling "itself"?
> Otherwise I'm afraid, I have some difficulties following you.
I mean that whereas (t)csh uses /bin/sh to run scripts with no
shebangs, the Posix-compatible shells execute scripts with no
shebangs directly. And this is Bad.
> > IMHO the Posix sh definition should be extended so that all
> > shells claiming Posix-compliance should do shebangs.
>
> Shells themselves should implement it, not the kernel?
It might be too much to ask the kernel to do, especially on
non-traditional Posix systems like z/OS.
> There was a working group resolution to standardize #!, which didn't
> make it, http://www.opengroup.org/platform/resolutions/bwg2000-004.html
> you could chime in
I see the problem now: a portable awk script, for example, can't assume
that the Posix awk is in /usr/bin/awk, so "#!/usr/bin/awk" might get the
wrong awk. So the feature is not worth standardizing for Posix.
--
[W]hen I wrote it I was more than a little John Cowan
febrile with foodpoisoning from an antique carrot cowan at ccil.org
that I foolishly ate out of an illjudged faith http://ccil.org/~cowan
in the benignancy of vegetables. --And Rosta
next prev parent reply other threads:[~2011-01-16 21:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 8:43 Warren Toomey
2011-01-16 9:55 ` John Cowan
2011-01-16 13:20 ` Sven Mascheck
2011-01-16 17:17 ` John Cowan
2011-01-16 19:19 ` Sven Mascheck
2011-01-16 20:17 ` John Cowan
2011-01-16 20:42 ` Larry McVoy
2011-01-16 21:08 ` Sven Mascheck
2011-01-16 21:37 ` John Cowan [this message]
2011-01-17 16:35 ` Warner Losh
2011-01-17 20:47 ` John Cowan
2011-01-17 10:09 ` Tim Bradshaw
2011-01-16 10:53 ` Wilko Bulte
2011-01-17 16:25 ` Warner Losh
2011-01-17 19:02 ` Jeremy C. Reed
2011-01-17 20:51 ` John Cowan
2011-01-17 22:41 ` Jeremy C. Reed
2011-01-17 20:58 ` Sven Mascheck
2011-01-19 4:10 ` Cyrille Lefevre
2011-01-19 20:35 ` Sven Mascheck
2011-01-20 4:09 ` Cyrille Lefevre
2011-01-28 19:38 ` Jeremy C. Reed
2011-01-30 15:05 ` Sven Mascheck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110116213738.GG3374@mercury.ccil.org \
--to=cowan@mercury.ccil.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).