> On Thu, Aug 30, 2012 at 7:56 PM, erik quanstrom <[email protected]> wrote: > >> The thing is that mk doesn't really do anything to set up connections > >> between the commands it runs. > > > > it does. the connections are through the file system. > > No. The order in which commands are run (or if they are run at all) > is based on file timestamps, so in that sense it uses the filesystem > for coordination, but mk itself doesn't do anything to facilitate > interprocess communications between the commands it runs (for example > setting up pipes between commands).
what i was saying is that mk knows and insures that the output files are there. the fact that it's not in the middle of the conversation is an implementation detail, imho. that is, mk is built on the assumption that programs communicate through files; $O^c communicates to $O^l by producing .$O files. mk rules know this. - erik
