On Wed, 18 Mar 2020, Sven Schreiber wrote:
Am 17.03.2020 um 21:49 schrieb Allin Cottrell:
> On Mon, 16 Mar 2020, Sven Schreiber wrote:
>>
>> 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.)
>
> The signature of funcerr() is now revised:
>
> first arg: boolean condition (non-zero means error)
> second arg: error message string
>
> Among the current function packages, only Artur's assertion.gfn uses the
> prior form (with a single string argument). That form is still accepted
> for now; to trigger the new form you must supply two arguments.
Excellent, thanks! If the single-argument form is supposed to go away
some day, then I'd suggest to make the first argument optional,
defaulting to True. (Not sure right now whether for built-in functions
we can write just a comma to leave that arg out, like we can with
user-defined functions that have defaults.)
Yes, that works, and it's now in git. But I think it's a bit
"irregular" to have an optional leading argument for a built-in
function so I haven't (yet) documented the optionality of the
boolean term.
Allin