[PD] Purr Data 2.4.7 released

2018-01-04 Thread Jonathan Wilkes via Pd-list
Purr Data 2.4.7 is available: https://github.com/jonwwilkes/purr-data/releases/tag/2.4.7 This is another bugfix release to keep Purr Data from freezing in certain situations with graph-on-parent patches* fix graph-on-parent issues with vumeter and radio objects * clean up the readme (t

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

2018-01-04 Thread IOhannes m zmölnig
On 01/05/2018 12:36 AM, IOhannes m zmölnig wrote: > repeat the test with two abstractions having loading libraries providing this should of course read: "having loading libraring providing". it's getting late... gfasmrd IOhannes signature.asc Description: OpenPGP digital signature

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

2018-01-04 Thread 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 us

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

2018-01-04 Thread Alexandre Torres Porres
how so? please elaborate... In my example I had a dummy abstraction in a lib listed in the path, but declare made it not call it. are you saying this only happens cause it is an abstraction? Because I made the test with a compiled object and I got the same behaviour, no difference! The compiled

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

2018-01-04 Thread IOhannes m zmölnig
On 01/04/2018 11:56 PM, Alexandre Torres Porres wrote: > Therefore, using [declare] will avoid name collisions and not the opposite. only for abstractions. gfadsmr IOhannes signature.asc Description: OpenPGP digital signature ___ Pd-list@lists.iem.at

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

2018-01-04 Thread Alexandre Torres Porres
2018-01-04 18:41 GMT-03:00, Christof Ressi : >> (is there a difference in behaviour between them?) > > stdlib is relative to the 'standard paths' whereas path is relative to the > current patch. > > my point is that the user could have their libraries in a totally different > place so that none of

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

2018-01-04 Thread Christof Ressi
> (is there a difference in behaviour between them?)   stdlib is relative to the 'standard paths' whereas path is relative to the current patch.   my point is that the user could have their libraries in a totally different place so that none of [declare -path/-stdpath/-lib/-stdlib cyclone] wil

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

2018-01-04 Thread Alexandre Torres Porres
2018-01-02 12:37 GMT-03:00 Christof Ressi : > what do you mean by [declare cyclone]? > > in case you mean [declare -stdpath cyclone]: > I meant adding a library as path or a lib, either in -stdpath / -path / -stdlib / -lib (is there a difference in behaviour between them?) > a) this would only

[PD] [PD-announce] NIME 2018 2nd call for submissions

2018-01-04 Thread Ivica Ico Bukvic
NIME 2018 Call for submissions Please pardon the cross-posting, *A friendly reminder of the upcoming submission deadline January 20th, 2018, for the NIME 2018 international conference. The paper templates and all other supporting information is available on the website (**NIME2018.ORG

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

2018-01-04 Thread tim vets
On Jan 3, 2018 10:24 PM, "Derek Kwan" wrote: "Christof Ressi" writes: >> and usually involves sort of prefixing or suffixing for every >> abstraction/external. > > I've also done this in the past. > namespacing by prepending the folder name has one advantage, though: > it provides you the possi