[PD] nosferatu namespaces (was: zexy and Pd-0.38.4-extended-RC3.app)
hans at eds.org
Wed Nov 23 18:24:20 CET 2005
On Nov 23, 2005, at 4:02 AM, IOhannes m zmoelnig wrote:
> Georg Holzmann wrote:
>> 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
> 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)
It is a miniscule bit of overhead for real interface rather than a
hack, and it would allow you to easily specify loading order. Plus
[using] would be able to load alternate lib formats like libdirs.
> 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.
This already exists. Its known as the "path". But it doesn't work for
the old lib format. Works fine with geiger namespaces/libdirs,
wherever objects are in single files.
"Information wants to be free."
More information about the Pd-list