I think (...) the correct thing to do is to correct it but 
> provide back compatibility

Everybody happy!

2015-11-25 14:31 GMT-02:00 Miller Puckette <msp@ucsd.edu>:
Sorry not to jump in before... I think in the case of this particular design flaw,
the correct thing to do is to correct it but provide back compatibility (as I
did earlier with hip~ and inlet~).  It's quite possible nobody will ever care but it
would be there in case someone did.

cheers
Miller

On Wed, Nov 25, 2015 at 04:25:49PM +0100, IOhannes m zmoelnig wrote:
> On 2015-11-25 12:37, Roman Haefeli wrote:
> > I fully support your opinion in this debate. If I'd be in charge, I'd
> > fix it right away.
>
> +1
>
> if you are doing glitch - and relying on a bug in a software to get
> those nifty sounds *is* glitch -, then you shan't complain if bugs get
> fixed¹.
>
> and of course: Pd is Open Source.
> if you cannot live without any given bug, fork the source and unfix the
> problem.
> or just use an old version of Pd that still inhibits the problem.
>
> fgmasdr
> IOhannes
>
> ¹ hey, why doesn't Pd crash any more? my entire performance relied on
> that...
>



> _______________________________________________
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list


_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list