[PD] [PD-announce] pd 0.48-1 released

To Pd-announce: Pd version 0.48-1 is available on http://msp.ucsd.edu/software.htm or (source only) via github: https://github.com/pure-data/pure-data cheers Miller ___ Pd-announce mailing list pd-annou...@lists.iem.at

Re: [PD] declare vs. namespaces - current best practice

+1 > Gesendet: Sonntag, 07. Januar 2018 um 20:58 Uhr > Von: "Lucas Cordiviola" > An: "pd-list@lists.iem.at" > Betreff: Re: [PD] declare vs. namespaces - current best practice > > I think Joao (the OP) is asking how to do in 2018 what he was doing

Re: [PD] declare vs. namespaces - current best practice

I think Joao (the OP) is asking how to do in 2018 what he was doing back on the “extended” years. IRRC he shares his lib which uses many other objects from other libs. Now there should be a proper way to do that with the cocktail “Deken, [declare] & namespace”. Deken - ? (only issue I know is

Re: [PD] declare vs. namespaces - current best practice

2018-01-04 20:36 GMT-03:00 IOhannes m zmölnig : > On 01/05/2018 12:17 AM, Alexandre Torres Porres wrote: > > > > The compiled object from the lib listed in the path doesn't get called, > and > > the one specified in [declare] gets called instead. > > > > repeat the test with two

Re: [PD] declare vs. namespaces - current best practice

2018-01-02 5:54 GMT-03:00 João Pais : > > Also: I imagine that there isn't a problem with repeated declarations? > Inside each abstraction there is a [declare], and a patch can always use > lots of them. > I don't think there is > > A suggestion: I can write [declare -stdlib