Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!andy From: andy@cbmvax.commodore.com (Andy Finkel) Newsgroups: comp.sys.amiga.programmer Subject: Re: CShell 5.10, arp stuff, A3000 w/2.0; should they go together Message-ID: <22111@cbmvax.commodore.com> Date: 3 Jun 91 14:12:25 GMT References: <1845@contex.contex.com> <37100008@hpfcdc.HP.COM> <22070@cbmvax.commodore.com> Reply-To: andy@cbmvax.commodore.com (Andy Finkel) Organization: Commodore, West Chester, PA Lines: 27 In article dillon@overload.Berkeley.CA.US (Matthew Dillon) writes: >In article <22070@cbmvax.commodore.com> andy@cbmvax.commodore.com (Andy Finkel) writes: >>In article dillon@overload.Berkeley.CA.US (Matthew Dillon) writes: >>Actually, Matt, the reason for the \n is to make any programs that >>call ReadArgs happy. ReadArgs uses the command line provided by >>the Shell via CurrentInput, and it requires that the line be >>terminated by a \n. >> >> andy > > Exactly. It's braindamaged. You shouldn't have to terminate your > argument line with a \n. :-) I agree. The reason is important, though, as most people won't run into it except when writing a shell, when they have to remember to set up the command line 'properly' before calling runcommand. They should know why and what will be affected. andy -- andy finkel {uunet|rutgers|amiga}!cbmvax!andy Commodore-Amiga, Inc. "If all you have is a hammer, everything looks like a popsicle." Any expressed opinions are mine; but feel free to share. I disclaim all responsibilities, all shapes, all sizes, all colors.