Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site callan.UUCP
Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!trwrb!scgvaxd!wlbr!callan!geoff
From: geoff@callan.UUCP
Newsgroups: net.unix-wizards
Subject: Re: /bin/sh feature?
Message-ID: <195@callan.UUCP>
Date: Fri, 20-Jul-84 00:22:10 EDT
Article-I.D.: callan.195
Posted: Fri Jul 20 00:22:10 1984
Date-Received: Sun, 15-Jul-84 09:44:29 EDT
References: <1370@ucf-cs.UUCP>
Organization: Callan Data Systems, Westlake Village, CA
Lines: 11

Regardless of the fact that there was an unmatched quote on the line with
the colon, why doesn't /bin/sh complain about the "unterminated" string?  I
don't especially mind it continuing past the unescaped newline (although
even that feature is poor design), but uncomplainingly taking the end of the
file as a matching quote is just plain sloppy programming--something you
find a lot in the Bourne shell.
-- 

	Geoff Kuenning
	Callan Data Systems
	...!ihnp4!wlbr!callan!geoff