Re: Error-safe user functions

On Mon, Dec 5, 2022 at 11:36 AM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:

>
> On 2022-12-05 Mo 11:20, Robert Haas wrote:
> > On Mon, Dec 5, 2022 at 11:09 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> >>> On Sat, Dec 3, 2022 at 10:57 PM Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
> wrote:
> >>>> 2. ereturn_* => errfeedback / error_feedback / feedback
> >>> Oh, I like that, especially errfeedback.
> >> efeedback? But TBH I do not think any of these are better than ereturn.
> > I do. Having a macro name that is "return" plus one character is going
> > to make people think that it returns. I predict that if you insist on
> > using that name people are still going to be making mistakes based on
> > that confusion 10 years from now.
> >
>
> OK, I take both this point and Tom's about trying to keep it the same
> length. So we need something that's 7 letters, doesn't say 'return' and
> preferably begins with 'e'. I modestly suggest 'eseterr', or if we like
> the 'feedback' idea 'efeedbk'.
>
>
>
Consulting https://www.thesaurus.com/browse/feedback again:
ereply clocks in at 7 characters.