From mboxrd@z Thu Jan 1 00:00:00 1970 From: michael@kjorling.se (Michael =?utf-8?B?S2rDtnJsaW5n?=) Date: Fri, 21 Apr 2017 13:20:22 +0000 Subject: [TUHS] Bourne shell and comments In-Reply-To: <201704210328.v3L3S6MI010851@freefriends.org> References: <20170418204834.GA22198@minnie.tuhs.org> <020a01d2b885$94bd49c0$be37dd40$@ronnatalie.com> <201704210328.v3L3S6MI010851@freefriends.org> Message-ID: <20170421132022.GA16779@yeono.kjorling.se> On 20 Apr 2017 21:28 -0600, from arnold at skeeve.com: >> 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. > > Perhaps reminiscent of the '!' escape to shell in ed and maybe > some other interactive programs of the time? That's purely a guess > on my part. How about that # could start a C preprocessor directive, but no C preprocessor directives begins with `!'? Makes it easy for the C compiler or preprocessor to check that it isn't being fed a random script. -- Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se “People who think they know everything really annoy those of us who know we don’t.” (Bjarne Stroustrup)