Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site maynard.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!talcott!wjh12!maynard!campbell
From: campbell@maynard.UUCP (Larry Campbell)
Newsgroups: net.unix-wizards
Subject: Re: # sign in shell/cshell scripts...
Message-ID: <284@maynard.UUCP>
Date: Thu, 17-Apr-86 18:37:22 EST
Article-I.D.: maynard.284
Posted: Thu Apr 17 18:37:22 1986
Date-Received: Sat, 19-Apr-86 14:19:58 EST
References: <237@Shasta.ARPA>
Organization: The Boston Software Works Inc., Maynard, MA
Lines: 18

> From: Alex Bronstein <ALEX@SU-SIERRA.ARPA>
> 	I'm encountering weird problems with sh (and sometimes csh)
> dying on some shell scripts depending on whether or not my first line in
> the script is a comment like:
> # This script does this (but not that)
> 
> 	I am looking for ANY hint/story/random knowledge concerning
> # in shell scripts.

Early versions of the Bourne shell (like the one shipped with VENIX 2.0)
did not recognize # as a comment delimiter -- in fact it didn't have ANY
comment delimiter.  I worked around this partially by creating a zero-length
executable file called /bin/#.  That works as long as there are no shell
metacharacters in the comment.  If there are, you're out of luck.
-- 
Larry Campbell                                 The Boston Software Works, Inc.
ARPA: maynard.UUCP:campbell@harvard.ARPA       120 Fulton Street
UUCP: {harvard,cbosgd}!wjh12!maynard!campbell  Boston MA 02109