Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!nathan
From: nathan@eddie.MIT.EDU (Nathan Glasser)
Newsgroups: comp.sys.ibm.pc
Subject: Re: NDMAKE 4.3 Bug?
Message-ID: <7229@eddie.MIT.EDU>
Date: Wed, 21-Oct-87 18:27:28 EDT
Article-I.D.: eddie.7229
Posted: Wed Oct 21 18:27:28 1987
Date-Received: Sat, 24-Oct-87 07:02:24 EDT
References: <15000037@silver> <15000040@silver>
Reply-To: nathan@eddie.MIT.EDU (Nathan Glasser)
Organization: MIT, EE/CS Computer Facilities, Cambridge, MA
Lines: 27

In article <15000040@silver> creps@silver.bacs.indiana.edu writes:
>   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.

Ok, I guess from ndmake semicolons do serve the intended puprose.

However, I want to point out an inaccuracy in the quoted manual
on this point.

>>     A.  This is because MAKE starts each command in the current directory.

This is the real reason why the semicolons are useful and necessary
for doing cd's and expecting to see the result.

>>     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"

This implies that cd is like set in that its effects are local to its
own shell (command.com), which is not correct.
-- 
				Nathan Glasser
fnord				nathan@{mit-eddie.uucp, xx.lcs.mit.edu}
"A tribble is the only love that money can buy."	    
Presently there is insufficient evidence to conclude that tribbles spread AIDS.