Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!utcs!lsuc!pesnta!hplabs!hao!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix
Subject: Re: commands within ``make''
Message-ID: <3295@umcp-cs.UUCP>
Date: Mon, 18-Feb-85 22:34:33 EST
Article-I.D.: umcp-cs.3295
Posted: Mon Feb 18 22:34:33 1985
Date-Received: Wed, 20-Feb-85 10:31:26 EST
References: <583@mako.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 24

> Is there a good reason why an option cannot be added
> to ``make'' so that it will directly execute subcommands
> such as the compiler, instead of invoking a subshell?

You could always make a system() routine that scanned its argument
for shell metacharacters, and if none were found, invoked programs
directly.

[Begin silliness]
Gee, you could even build in file name pattern matching, pipes, hey
even backquote, and...  f we put enough work in it, the shell itself
becomes:

	main () {
		while(fgets(input, sizeof input, sdtin) != NULL)
			system(buf);
		exit (0);
	}

!
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	{seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@maryland