[PD] another [declare -lib] strangeness

2008-01-23 Thread IOhannes m zmoelnig
hi originally i wanted to write the following feature-request: using [declare] to load libraries (e.g. [declare -lib mylib]) works nicely. however, when i have several abstractions all depending on the same library (and thus all have an instance of [declare -lib mylib]), i get an error mylib:

Re: [PD] another [declare -lib] strangeness

2008-01-23 Thread Miller Puckette
No, I never tried, thinking, as I do, that it couldn't possibly work :) Anyway, I can't imagine changing it so close to a release, since anything that could be considered correct would take months of testing to get working correctly, so, like it or not, I think I have to try to figure out what it

Re: [PD] another [declare -lib] strangeness

2008-01-23 Thread Roman Haefeli
On Wed, 2008-01-23 at 10:54 -0800, Miller Puckette wrote: No, I never tried, thinking, as I do, that it couldn't possibly work :) Anyway, I can't imagine changing it so close to a release, since anything that could be considered correct would take months of testing to get working correctly,

Re: [PD] another [declare -lib] strangeness

2008-01-23 Thread Miller Puckette
good news! if i can help you in anyway (e.g. documenting as accurately as possible how [declare] behaves), i'd be glad to do so. i am very much convinced, that [declare] is a useful class and worth a lot of effort to make it work. roman Yeah, I find it very useful too. (even

Re: [PD] another [declare -lib] strangeness

2008-01-23 Thread Hans-Christoph Steiner
I think very few people are using [declare]. I think Pd would be much better off with a well functioning [declare] than just freezing the current functionality. .hc On Jan 23, 2008, at 1:54 PM, Miller Puckette wrote: No, I never tried, thinking, as I do, that it couldn't possibly work