ok, but let me be picky... first, [declare -lib] loads a library, relative to the patch, so there seems to be no reason to declare it if it is in the same folder as the patch and I could just call it by [./scope~], right?
But well, if you actually mean using [declare -stdlib], same thing goes... i can just call it [cyclone/scope~], instead of [declare -stdlib cyclone/scope~] and then using just [scope~]. So this is why I don't see a point in using declare, even though you can. Seems like it's useful if you're loading a library like zexy.
Moreover, it's nice just to have cyclone folder in your search path and don't bother to use declare -lib or -path
But anyway, I have my compiled single object library scope~.pd_darwin
I tried [declare -stdlib cyclone/Scope~] and I could load the object in the following manners:
[scope~] [Scope~] [cyclone/scope~] [cyclone/Scope~]
which are also the 4 ways I can load it if I just have it in my search path
So, did I find a good way to phase out the Upper Case Letter NonSense? :)
cheers
2016-04-08 19:11 GMT-03:00 IOhannes m zmölnig zmoelnig@iem.at:
On 04/09/2016 12:06 AM, Alexandre Torres Porres wrote:
sure, but not a library containing many objects, so I don't see why using [declare -lib], isn't that just for the case of libraries with many objects? Since it is just a single object binary, all I need is to have
it
in a path, so more like [declare -path "folder"].
well the point is that you *can* load any library (regardless of the number of object it contains) with [declare -lib].
e.g. you can use it to load a library "cyclone/Scope~" which has an alias "scope~" - and in the patch you can juse use [scope~].
gmdsr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list