So, what solutions do I have for my problem?  If I cannot put more than ten zexy externals to load at startup, do I need to just put zexy.pd_darwin back into my extras folder and load it?  While creating objects neamed [Gem] or [pmpd] might work, [zexy] won't do anything until I have zexy.pd_darwin in my extras folder.  This leads me to my last question:  libraries and externals (like [z~]) can be loaded through the Startup script, while only libraries can be loaded with a [library] object being placed in a patch, right?

I appreciate having all the zexy objects separated to keep the RAM usage down, but it seems to complicate things a bit.  Unless anyone has a better solution, I'm just going to stick zexy.pd_darwin back in my extras folder and load that.

sb



On Nov 23, 2005, at 4:02 AM, IOhannes m zmoelnig wrote:

Georg Holzmann wrote:
Hallo!
well, this would be useful, but whats the difference from [using zexy] to [zexy] - it also loads the lib because most libs implemented such a dummy object (or at least some) ?

note that the library does not have to implement an object of the same name. e.g. there is no [Gem] object in Gem, but you still can load Gem by creating an object [Gem]: the creation will fail but Gem will be loaded.

so you are correct, that using [using] just for library loading is a bit of an overhead (especially since people tend to externals instead of libraries)

i think that the [using] object should automatically add (an optional) library-prefix to objects that cannot be found.
imagine you have a patch that contains [using zexy] (how comes this discussion always concentrates on my libraries...) and [nop].
since pd cannot find a [nop] object anywhere in it's space, it would try to find [zexy/nop] which eventually is an abstraction ./extra/zexy/nop.pd and thus can be resolved and loaded.



mfg.asd.r
IOhannes

oops, i see we are in the never ending namespace discussion again and thus change the subject accordingly