I meant, in the end, compile everything (Pd, libpd and externals) with PDINSTANCE/PDTHREADS and give up specific single thread code. Of course this won't magically make every external suitable for multiple threads of contexts... But at least there will be only one binary interface.
Antoine Le lun. 29 juin 2026 à 17:13, IOhannes m zmölnig via Pd-dev < [email protected]> a écrit : > On 29/06/2026 14:30, Antoine Rousseau wrote: > > However, I have wondered whether it might be possible, in the future, to > > achieve a convergence between multiple-instance and single-instance code. > > That is: always compile libpd with PDINSTANCE/PDTHREADS flags (then just > > remove them), and the same for Pd. I think the overhead is negligible. > > > > my thoughts (about convergence). > > though i don't know what exactly you mean with: > > always compile libpd with PDINSTANCE/PDTHREADS flags (then just > > remove them) > > something like: compile libpd (and eventually Pd itself?) with > PDINSTANCE/PDTHREADS, but allow externals to be compiled without these > flags? > that probably wouldn't allow for the externals to be used in a > multi-context/multi-threaded runtime, but at least it would be possible > to use them in single-context mode by a multi-context *capable* runtime. > > i guess this is something i would like to have as an intermediate step > (until all externals are multi-context capable). > one question is of course, which class of hard-to-find bugs this would > open up. > > gmdsar > IOhannes > --- > [email protected] - the Pd developers' mailinglist > > https://lists.iem.at/hyperkitty/list/[email protected]/message/IJUWCSPL25Q7XBX4AZX6GN7IUNIMKVEK/
--- [email protected] - the Pd developers' mailinglist https://lists.iem.at/hyperkitty/list/[email protected]/message/LJVQOLBJDSVJFLSQFTQUUA3KLXLGAJLH/
