Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!ncrlnk!wright!sdawalt
From: sdawalt@wright.EDU (Shane Dawalt)
Newsgroups: comp.lang.c
Subject: Re: MSC 5.1 make
Message-ID: <888@thor.wright.EDU>
Date: 20 Dec 89 19:04:42 GMT
References: <8178@cg-atla.UUCP>
Organization: Wright State University, Dayton OH, 45435
Lines: 29

in article <8178@cg-atla.UUCP>, fredex@cg-atla.UUCP (Fred Smith) says:
> 
> In article <884@thor.wright.EDU> sdawalt@wright.EDU (Shane Dawalt) writes:
>>                                       I suspect that Microsoft may have
>>relaxed the strict rule flow of Unix so that non-Unix users could simply
                               ^^^^^^^
>>list their files in any order and make would run without problems ... then
>>you have the Unix people wondering why MSC's make is so "strange."  :-)
>>
>>  Shane
>>
>>sdawalt@cs.wright.edu
> 
> What MSC's make does is to move the dependency order work from the program
> to the PROGRAMMER. It is necessary for the objects to be listed in the makefile
> top to bottom in dependency order.

  Perhaps I did not choose the best wording (I can almost see everyone
nodding their heads), but when I stated "strict rule flow of Unix [make],"
the implication was a recursive, top-down ordering of rules in the makefile as
is required for Unix make.  Microsoft make starts at the top and works down the
rule list one at a time.  That's terrific for non-Unix people; just list the
files in the makefile (source first, executable last) and ya have it made.  On
the other hand, the concept of a make utility is not realized with this type
of makefile format.

  Shane

email: sdawalt@cs.wright.edu