[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34338: 26.1; delete-file return codes and failures
From: |
Boruch Baum |
Subject: |
bug#34338: 26.1; delete-file return codes and failures |
Date: |
Wed, 30 Oct 2019 21:33:29 -0400 |
User-agent: |
NeoMutt/20180716 |
On 2019-10-30 23:52, Stefan Kangas wrote:
> Boruch Baum <boruch_baum@gmx.com> writes:
>
> Do you have a use-case in mind here? Can't the caller just check using
> 'file-exists-p' if it matters instead?
It _should_ *always* matter. Did you delete the file or not? If it didn't
matter, why waste your time attempting the deletion?
Having delete-file return the value is: a) consistent with what I think
is the expectation of most CS folks; b) the most efficient, since it
already knows the exact point of any failure, and basically just passes
the return value it gets from the underlying OS.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0