Yeah it's possible to have code that works for both. And I do agree it
makes good sense in some cases like the single vstplugin~ external.
But not in ELSE though and I guess you weren't asking this so I shouldn't
say anything, but here it goes anyway just in case. I'm not happy with the
idea of do
Actually, I think we could streamline this process with a new API
function: https://github.com/pure-data/pure-data/issues/2075
On 04.08.2023 23:16, Christof Ressi wrote:
To avoid bleeding-edge red, is the following not possible with externals?
This would work in a way that you could compile E
To avoid bleeding-edge red, is the following not possible with externals?
This would work in a way that you could compile ELSE for older Pd
versions. But then you would essentially need to ship two different
versions: one for Pd 0.54> and another one for Pd 0.54<=.
Ideally, there should be one
To avoid bleeding-edge red, is the following not possible with externals?
#ifdef PD_MAJOR_VERSION >= 0 and PD_MINOR_VERSION >= 54
// multichannel code
#else
// non-multichannel code
#endif
Depending upon the code layout, you could also probably use some macros for
lots of redundant stuff.
> On