> > how long does it take you to run mk, and then realise you didn't Put your
> > last set of changes?

> > i once changed mk on my local machine to act as you suggest, and then
> > took far too long trying to figure out why the program's behavior didn't
> > reflect the code. more time than i saved from waiting on mk? who knows?

> If the situation you describe can happen then it definitely shouldn't be
> changed.  Could you please provide me with a scenario (sequence of events)
> that would be a problem if mk was changed?  I can't think of one.

i thought i just described one in acme:

change stuff
middle click Put
change more stuff
middle click mk

middle click Put (within the same second of a file's compile)
middle click mk (don't notice that the file wasn't recompiled)

tristan

--
All original matter is hereby placed immediately under the public domain.