Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!boulder!sunybcs!rutgers!iuvax!silver!creps
From: creps@silver.bacs.indiana.edu
Newsgroups: comp.sys.ibm.pc
Subject: Re: NDMAKE 4.3 Bug?
Message-ID: <15000040@silver>
Date: Wed, 21-Oct-87 16:04:00 EDT
Article-I.D.: silver.15000040
Posted: Wed Oct 21 16:04:00 1987
Date-Received: Sat, 24-Oct-87 06:23:45 EDT
References: <15000037@silver>
Organization: Indiana University BACS, Bloomington
Lines: 39
Nf-ID: #R:silver:15000037:silver:15000040:000:1788
Nf-From: silver.bacs.indiana.edu!creps    Oct 21 15:04:00 1987


>/* Written  4:17 pm  Oct 20, 1987 by nathan@mit-eddie in silver:comp.sys.ibm
>
>From a comment creps@silver made above and others I didn't include,
>it seems that he does not use the standard command.com. The one
>he does use apparently remembers the current directory when it
>starts, and changes back to this directory at the termination.
>
>His solution also does not apply to standard command.com. Semicolons
>do not serve to separate commands on a single command line, nor is
>there any other way to do this.

   For the record, I am using the standard command.com. No, semicolons don't
separate commands on a line in DOS, but they DO in ndmake. Here is the exact
text from the ndmake 4.3 documentation. I hope it ends this discussion once
and for all.

>     MAKE supports multiple commands on a single line if the command is
>     enclosed in parentheses () and the commands are separated by semi-
>     colons (use \; if you need a semi-colon to *not* be interpreted as a
>     command separator).  In fact, since each command line is executed in
>     its own shell, this is the only way to use DOS commands like "set" and
>     "chdir" so that they have any effect.  For example, doing "make x"
>     where the makefile looks like:
>          x:
>               chdir \tmp
>               copy *.* a:
>     
>     will copy the contents of the *current* directory, not \tmp, to drive
>     A.  This is because MAKE starts each command in the current directory.
>     The correct way to write this is:
>          x:
>               (chdir \tmp; copy *.* a:)

-	-	-	-	-	-	-	-	-
Steve Creps on the VAX 8650 running Ultrix 2.0-1 at Indiana University.
	creps@silver.bacs.indiana.edu
"...and I noticed the lad with the thermonuclear device was the Chief Constable
 for the area..."