> > 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.
>
> Would you like to get notified if such instances are found?
>
> Roman
I'm about to can the error() function
On Fri, 2021-08-20 at 12:42 -0700, Miller Puckette wrote:
> 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
>
On Sat, Aug 21, 2021 at 01:32:10PM +0200, Christof Ressi wrote:
> > My understanding has always been: m_pd.h is public and generally
> > shouldn't change without some sort of compatibility coverage. Anything
> > other .h is private.
> That's the theory. On the other hand, many functions/variables
My understanding has always been: m_pd.h is public and generally
shouldn't change without some sort of compatibility coverage. Anything
other .h is private.
That's the theory. On the other hand, many functions/variables in
"g_all_guis.h", "s_stuff.h" and "m_imp.h" are marked as "EXTERN" (which
My understanding has always been: m_pd.h is public and generally shouldn't
change without some sort of compatibility coverage. Anything other .h is
private. I wrote d_soundfile.h and s_net.h as private headers, but they could
be included in m_pd.h to make them public for example. We could add
Well, the functions are still there so binary compatibility should be OK.
But I bet there's other stuff that got broken.
(I think binary compatibility is more important than source compatibility
because one can always update sources - the chief reason you need them is in
order to recompile
I bet a lot of other stuff will turn out to be broken, hmm.
get_sys_sleepgrain() and the just removed:
EXTERN void sys_clearhist(void);
EXTERN int sys_addhist(int phase);
will surely break Pdvst~
From looking at:
https://github.com/jyg/PdVst/search?q=sys_clearhist
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").
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: ...
