Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[9fans] mk: the `D' attribute

14 views
Skip to first unread message

dexen deVries

unread,
Oct 9, 2012, 4:02:54 AM10/9/12
to
why is the `D' attribute (`If the recipe exits with a non-null status, the
target is deleted.') optional and not default behavior? in what cases does
leaving half-made files make sense?

GNU make's manual states, ``This [[removal of target on error]] is almost
always what you want `make' to do, but it is not historical practice; so for
compatibility, you must explicitly request it''. is `mk' about backward
compatibility just as well?

--
dexen deVries

[[[↓][→]]]

Andy Spencer

unread,
Oct 9, 2012, 5:04:15 AM10/9/12
to
On 2012-10-09 10:02, dexen deVries wrote:
> GNU make's manual states, ``This [[removal of target on error]] is
> almost always what you want `make' to do

I'm don't think GNU Make has ever correctly predicted what I want
`make' to do.

Besides that, I think there could be problems if you have an existing
file and run mk to update it and instead it just deletes the one you
have.

Anthony Sorace

unread,
Oct 9, 2012, 11:22:37 AM10/9/12
to
I suspect it just that we disagree. In the most common case, I don't really
care whether such things get deleted. I sometimes very much want them
not to be deleted, because they contain interesting information on the
failure mode. I don't believe I've ever explicitly wanted them to be
deleted. That describes a good case for the current default behavior.

Anthony

0 new messages