[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 https://lists.puredata.info/listinfo/pd-announce ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
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 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 troubles adding path for pkgs that have > “-” in its name) > > [Declare] - We should review > https://github.com/pure-data/pure-data/pull/205 because the proposed: > > 1: search relatively to the calling patch > 2: search the user's global paths > 3: search Pd's system paths > > Is a good one. > > Namespace – Single binary libs should provide a way call [obj] using > namespace. > > > > -- > > Mensaje telepatico asistido por maquinas. > > ___ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
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 troubles adding path for pkgs that have “-” in its name) [Declare] - We should review https://github.com/pure-data/pure-data/pull/205 because the proposed: 1: search relatively to the calling patch 2: search the user's global paths 3: search Pd's system paths Is a good one. Namespace – Single binary libs should provide a way call [obj] using namespace. -- Mensaje telepatico asistido por maquinas. ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
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 abstractions having loading libraries providing > the same object. > e.g. abs1.pd uses a [gate] stub that prints "gate 1", whereas abs2.pd > uses a [gate] stub that prints "gate 2". > load abs1.pd, after that abs2.pd (either manually, or by putting them > into a master patch). observe the console. > ok, I actually have to say I don't get what this is supposed to test. I just get "gate1" and "gate2" as I would expect and I don't see how it relates to the previous discussion. Now, since I have already replied to this giving the idea that I understood it and that it made me see things I didn't know, I have to explain that I had found them on my own and just assumed we were talking about the same thing. But now that I actually tried to check it, I don't. Sorry for the confusion. I'm actually on vacation visiting paradisiac beaches of the brazilian northeast and shouldn't be trying to find time to keep up with this :) cheers ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
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 x], and there will be no > error message warning that the x library doesn't exist. Would it be > good to have an error message, or even open deken to search for it? > added a request https://github.com/pure-data/pure-data/issues/281 ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list