TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
X-To: "David C. Hoos" <[log in to unmask]>
Date: Fri, 15 Oct 1999 20:39:49 -0400
Reply-To: Steven Deller <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
From: Steven Deller <[log in to unmask]>
Parts/Attachments: text/plain (36 lines)
> > >   (a) What if you want the csh instead of the sh?
> >
> > Not possible through POSIX.
> >
> Not correct.  You issue the command string
> "csh -c <single-parameter>", so the "sh" shell executes
> csh with the appropriate single string parameter -- i.e.,
> quoting, or escaping, or whatever to make the string
> passed to csh a single parameter as far as sh is concerned.
> Then csh will parse that single string.
> For a concrete example "csh -c 'cp file_a file_b'"
> or  "csh -c cp\ file_a\\ file_b"
> I do this all the time (with tcsh), because I find the
> syntax of tcsh/csh easier to rememeber than the Bourne Shell.

Well, to split a hair, much like we are used to doing with the RM...

While the above works most places, I do not believe it is ensured to be
portable on a POSIX compliant system.  If you want to stay within POSIX then
it is not possible.  That is, "csh" is not required for a POSIX compliant

CAVEAT: I don't have the latest POSIX documents, so perhaps "csh" or "tcsh"
have been added.


Steven Deller, Apex Ada Marketing
[log in to unmask], (410) 757 6924
Rational Software Corporation,
For user email groups, check