Am 16.03.2020 um 22:21 schrieb Allin Cottrell:
function-variant of "catch", as in
catch(maybe_bogus_input, "can't do that")
meaning: if the antecedent is true, do funcerr with the consequent as
error message.
Either way it's an overloading and I'm not sure my suggestion is better,
but to my mind it's more logical to put the condition first, then the
response, and we can't prepend an argument to funcerr without backward
incompatibility.
That's exactly what I was thinking, too. OTOH funcerr() was introduced
less than 3 months ago (not counting the pre-release phase), so maybe it
wouldn't be too bad to break compatibility here? (After a thorough check
of the packages, of course.)
cheers
sven