You can use the library prefix to guarantee that it uses the class
that you want. In the Pd-extended builds, everything is arranged
like this: [mylibrary/myobject]

.hc

On Sep 6, 2006, at 11:18 AM, Mike McGonagle wrote:

Hello all,

I recently returned to using Pure Data, and in trying to consolidate some of the things that I am doing, I started to create a directory structure of my abstractions and externals. One thing that I noticed (by accident) is that once I have loaded an external using the full directory name, it is then subsequently available by just referencing the name of the external, without the full directory name.

Is this something that is intentional? Is this something that can be used to, in effect, create a "library" of externals for various different platforms? I can see this working by loading all the necessary externals by their full directory paths, and then the *.pd files that use those externals would just call it by the name of the external.

How can name clashes be prevented? Can that only be stopped by giving the full directory path to the external?

Thanks,

Mike

---

PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list

"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away to benefit those who profit from
scarcity." -John Gilmore