Follow-up Comment #5, bug #20394 (project make):
Timestamps are a different matter, gmake doesn't use the cache to check
timestamps of files. Also, what I meant was *chained* rules with intermediate
files, not first-level implicit rules. Basically it is so that gmakes spends
all win from the cache on it's own built-in chained and match-anything rules.
For the user the cache brings no benefit, only the known inconsistencies.
However it is maybe right that two different behaviours is too confusing.
Probably it would be better to use no cache at all and get rid of some exotic
built-in rules instead.
As to empty the cache after each subprocess, well it could work too. I don't
quite see the deal with the counter though, shouldn't a boolean 'is_stale'
suffice?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?20394>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
