Am 5. April 2025 15:12:40 MESZ schrieb Miller Puckette via Pd-dev pd-dev@lists.iem.at:
Incidentally I'm planning to break my own rule to update 0.55 to be compatible with externs that use pd_class_new() so that people can compile externs that work both in 0.55 and in VSTs. That's more a compatibility enhancement than a bug fix.
personally I would: - start exporting `pd_class_new` as soon as possible (but without necessarily making it part of the public API as exposed in the headers) - LATER turn `class_new()` into a macro that points to `pd_class_new()` resp `pd_class_new64()`, depending on the floatsize. (similar to what we already do for Pd64).
"LATER" needs to take a while, so people can still run their newly compiled externals on older Pds.
I'm not overly enthusiastic about externals starting to explicitly use that new symbol.
mfg.sfg.jfd IOhannes