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