The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Bourne shell and comments
Date: Thu, 20 Apr 2017 16:13:18 -0400	[thread overview]
Message-ID: <CAC20D2Pbv3Hkvmz_=G3Hh9PjoDQQb1GcYf0ZwvTQ7tu6BP447g@mail.gmail.com> (raw)
In-Reply-To: <020a01d2b885$94bd49c0$be37dd40$@ronnatalie.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

below...

On Tue, Apr 18, 2017 at 4:51 PM, Ron Natalie <ron at ronnatalie.com> wrote:

> I believe the Berkeley #! magic number came first.

​That's right....​ the #!path syntax was BSDism that went main stream
because of its usefulness with "little languages" not just the shell.
 I'd have to check the tapes but it may have gone back as far as the
original BSD ~77/78 - Ken would have brought it back after his sabbatical
(or not - he would have seen it).

The # was nod to the # being the first characters of the C program to say
to use the preprocessor; but I've forgotten why the bang was added before
the path.    It could have been almost anything.

But the #!path syntax really was a great idea and opened up a lot of
different pseudo built-in scripting languages we think go with UNIX today.
But back in the day, their were not that many to start.




> The C Shell already
> ​ ​
> used this as a comment,

​exactly.​


> the Bourne shells grudgingly followed.
>
​Yep - although, like Warren I don't remember how soon.   The thing was you
programmed to V7 [Bourne] syntax and typed to C shell [I still do - the
rom's in the my fingers are not erasable].   I do remember commenting
Bourne scripts, so it must have come early in the Vax line, although its
strange the 2.x did not pick it up, until it seems 2.11 which is pretty
late.



>
> I still remember using : for a comment in the V6 shell.   Was also the
> label
> for goto.
>
​Yep - I remember that also - it worked...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170420/037338b8/attachment-0001.html>


  parent reply	other threads:[~2017-04-20 20:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 20:48 Warren Toomey
2017-04-18 20:51 ` Ron Natalie
2017-04-18 21:45   ` Grant Taylor
2017-04-18 22:16     ` Ron Natalie
2017-04-18 22:40       ` Toby Thain
2017-04-19 18:36     ` Stephen Kitt
2017-04-19 20:35       ` Arthur Krewat
2017-04-19  0:50   ` Lyndon Nerenberg
2017-04-19  8:35     ` Andreas Kusalananda Kähäri
2017-04-19 16:31     ` Grant Taylor
2017-04-19 16:59       ` Andreas Kusalananda Kähäri
2017-04-19 17:36       ` Bakul Shah
2017-04-19 17:59         ` Grant Taylor
2017-04-20 20:13   ` Clem Cole [this message]
2017-04-20 20:17     ` Chet Ramey
2017-04-21  3:28     ` arnold
2017-04-21  3:43       ` Bakul Shah
2017-04-21  6:07         ` Steve Nickolas
2017-04-21 11:18       ` Clem cole
2017-04-21 13:20       ` Michael Kjörling
2017-04-18 20:56 ` Chet Ramey
2017-04-19 21:02 ` Sven Mascheck
2017-04-19 22:07   ` Steffen Nurpmeso
2017-04-20  0:31     ` shawn wilson
2017-04-20  0:35       ` shawn wilson
2017-04-20  3:50         ` Andy Kosela
2017-04-20  4:47           ` Warner Losh
2017-04-21  1:42             ` Nemo
2017-04-21 10:54               ` Ron Natalie
2017-04-21 14:22                 ` Andy Kosela
2017-04-21 14:45                   ` Ron Natalie
2017-04-22  2:46           ` Dave Horsfall
2017-04-20 16:39     ` Sven Mascheck
2017-04-20 21:42       ` Steffen Nurpmeso
2017-04-19 19:18 Doug McIlroy
2017-04-21 17:03 Doug McIlroy
2017-04-21 18:15 ` Clem Cole
2017-04-21 19:13   ` Steve Johnson

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='CAC20D2Pbv3Hkvmz_=G3Hh9PjoDQQb1GcYf0ZwvTQ7tu6BP447g@mail.gmail.com' \
    --to=clemc@ccc.com \
    /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).