Article View: comp.std.unix
Article #729Re: Shell standardization (for c.std.unix)
From: Doug Gwyn
Date: Thu, 31 Jan 1991 19:08
Date: Thu, 31 Jan 1991 19:08
19 lines
1392 bytes
1392 bytes
Submitted-by: gwyn@smoke.brl.mil (Doug Gwyn) In article <17504@cs.utexas.edu> karish@mindcraft.com (Chuck Karish) writes: >On some older SysV-based systems I've used, scripts that start with the '#' >character are interpreted as csh scripts no matter what follows the '#'. That was a bug in porting a pre-#! era csh feature. On UNIX System V, more often than not Bourne shell scripts begin with '#'. Therefore it was unwise to leave that vestigial feature in csh when porting it to such an environment. The basic answer is that there is no truly portable solution, other than writing Bourne shell scripts starting with non-# that invoke whatever other command is actually wanted, using some sort of path search to find it. Of course Plan 9's user-mounted appendable directories makes this easier.. Volume-Number: Volume 22, Number 95
Technical Details
Message-ID:
<17530@cs.utexas.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!jsqReferences:
<17155@cs.utexas.edu> <17400@cs.utexas.edu> <17504@cs.utexas.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!jsq From: gwyn@smoke.brl.mil (Doug Gwyn) Newsgroups: comp.std.unix Subject: Re: Shell standardization (for c.std.unix) Message-ID: <17530@cs.utexas.edu> Date: 31 Jan 91 19:08:05 GMT References: <17155@cs.utexas.edu> <17400@cs.utexas.edu> <17504@cs.utexas.edu> Sender: jsq@cs.utexas.edu Organization: U.S. Army Ballistic Research Laboratory, APG, MD. Lines: 19 Approved: jsq@cs.utexas.edu (Moderator, John S. Quarterman) X-Submissions: std-unix@uunet.uu.net