Well, I've never been able to articulate a clear and complete policy... Roughly speaking, I'm maintaining source and binary compatibility for anything that uses the public API (m_pd.h) and trying not to break things that use private APIs (g_vanas.h, s_stuff.h and, privater still, m_imp.h"). Meanwhile there's a profusion of ".h" files I didn't write (d_soundfile.h, g_all_guis.h, etc) that I've never formed a policy for.
In the case of get_sys_sleepgrain() I can write a new implementation that should work - in fact that might even be a good idea fro otehr reasons :) - but there's a lot more that I've changed in s_stuff.h, since I've revamped the whole audio interface. I bet a lot of other stuff will turn out to be broken, hmm. Miller On Fri, Aug 20, 2021 at 05:23:18PM +0200, Roman Haefeli wrote: > Hi all > > I just compiled Pd from master and found that I cannot load [fifop] > from zexy anymore. When loading it, I get: > > ~~~ > error: /home/roman/Documents/Pd/externals/zexy/zexy.pd_linux: > /home/roman/Documents/Pd/externals/zexy/zexy.pd_linux: undefined symbol: > get_sys_sleepgrain > fifop > error: ... couldn't create > ~~~ > > I believe the related commit in Pd is 95b61465. > > I haven't tried re-compiling zexy yet, because I am under the > impression that Pd shouldn't break existing externals. I'm using 2.3.1 > from Deken. > > Roman > > > > _______________________________________________ > Pd-dev mailing list > [email protected] > https://lists.puredata.info/listinfo/pd-dev -- _______________________________________________ Pd-dev mailing list [email protected] https://lists.puredata.info/listinfo/pd-dev
