Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site bbncc5.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!bbnccv!bbncc5!cspencer
From: cspencer@bbncc5.UUCP (Clifford Spencer)
Newsgroups: net.unix,net.unix-wizards
Subject: Re: Bourne shell modifications, past and future (long)
Message-ID: <3@bbncc5.UUCP>
Date: Sat, 16-Nov-85 17:32:07 EST
Article-I.D.: bbncc5.3
Posted: Sat Nov 16 17:32:07 1985
Date-Received: Mon, 18-Nov-85 07:53:13 EST
References: <1943@gatech.CSNET> <10@druri.UUCP> <21@pixdoc.UUCP>
Organization: Bolt Beranek and Newman, Cambridge, MA
Lines: 14
Xref: watmath net.unix:6270 net.unix-wizards:15758

> > Out of curiosity, just why don't you want to put in command aliasing?
> It's there, called shell functions!  e.g.:
> 	l () { ls -FCs $* ; }
I think the most glaring difference between csh aliasing and
sys5 bourne shell functions is that the latter looks up builtins first.
This means you can't define functions that clash with shell commands.
On the other hand shell functions have a MUCH better syntax. Why not
move up the expansion of shell functions ahead of builtins at
the expense of not having recursive functions.
					-cliff
-- 
cliff spencer
{harvard, ihnp4, decvax}!bbnccv!cspencer
cspencer@bbncc5