Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!paperboy!meissner From: meissner@osf.org (Michael Meissner) Newsgroups: comp.unix.shell Subject: Re: "Modern" sh (was Math routines) Message-ID: Date: 2 Sep 90 23:46:13 GMT References: <26DC6447.15922@maccs.dcss.mcmaster.ca> <8446@orca.wv.tek.com> <75@iconsys> <2494@uc.msc.umn.edu> Sender: news@OSF.ORG Organization: Open Software Foundation Lines: 36 In-reply-to: bglenden@mandrill.cv.nrao.edu's message of 2 Sep 90 21:24:41 GMT In article bglenden@mandrill.cv.nrao.edu (Brian Glendenning) writes: | All this reminds me of questions I've been meaning to ask: | | 1) Are there any versions of sh that don't understand # comments any | more? It depends on when the last time you installed the system. If it was 1979 or such, then your shell probably doesn't understand # comments (I don't remember whether it was in the v7 shell, or not). But seriously, there are probably people running ancient systems out there that are stuck because their vendor went belly up years ago (of course you could probably buy a 386 running UNIX nowadays for a fraction of the original cost, but if you don't have the $5-10K at the present time, it doesn't matter). | 2) How common are sh's that don't understand shell functions? Anything that is BSD based without adding from System V. For example, the Ultrix DECstation that I'm posting from has the musty BSD shell as /bin/sh and the System V.2 shell with shell functions as /bin/sh5. Another problem with the BSD shell Ultrix uses, is that test (aka '[') is a separate command that you have to fork/exec to get to -- I suspect echo is too..... | I'm particularly interested in the answer for machines that scientists | are apt to buy and use (so that old PDP-11 in your closet doesn't | count!) You could always recomend bash and/or ksh. -- Michael Meissner email: meissner@osf.org phone: 617-621-8861 Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142 Do apple growers tell their kids money doesn't grow on bushes?