You missed the discussion because it took place in libpd-land: https://github.com/libpd/libpd/issues/336

It was not a decision taken lightly, but it's necessary as Pd's previous "error()" could conflict with libc "error()". The replacement already existed for sometime, so changing calls to "error(...)" with "pd_error(0, ...)" should be equivalent and not break the external in old versions of Pd.

On Apr 29, 2022, at 12:00 PM, pd-dev-request@lists.iem.at wrote:

Message: 2
Date: Fri, 29 Apr 2022 09:51:48 +0200
From: Roman Haefeli <reduzent@gmail.com>
To: pd-dev@lists.iem.at
Subject: [PD-dev] error missing in Pd 0.52
Message-ID: <96224f3ab47171eff50b17d1507974c6d8b13fd5.camel@gmail.com>
Content-Type: text/plain; charset="utf-8"

Hey all

Since 0.52, compiling of some externals fails with an error like:

~~
binfile.c:103:9: error: implicit declaration of function 'error' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
       error("binfile: Could not create...");
~~~

In 0.51-4, the error function was still defined in m_pd.h. Was 'error'
deprecated in favor of pd_error?

Sorry, if I missed the related discussions, but I feel introducing
breaking  changes in Pd is generally not done lightly. And I found
similar issues in active developments like aoo, so I'm probably not the
only one having missed this.

Roman

--------
Dan Wilcox
@danomatika
danomatika.com
robotcowboy.com