On Mon, 4 Aug 2003, Hans-Christoph Steiner wrote:
On Thursday, Jul 31, 2003, at 18:30 America/New_York, guenter geiger wrote:
On Thu, 31 Jul 2003, Hans-Christoph Steiner wrote:
I would quite prefer it, if the comb one gets renamed. It will irritate users coming from languages like Csound. (It did irr. me)
Sounds good to me. [reson~] from Gem/cxc was relatively buried and undocumented, so I can't imagine that it got much use.
Hi,
Well, I don 't have to say that I think that the work you are doing is very valuable. For the externals that get trashed, I suggest that instead of renaming them (which would only be of any help if someone wants to use them in a new project). ....
... we just put them in a new folder "deprecated" (or the like). The advantage of this is that people who have old patches around using these objects can select the deprecated version just by adding a path to that folder, and they don't have to rename objects in their old patches.
The order pd searches for externals (abstractions) is:
*) externals come first
- in local directory (dir of the patch)
- in the path
- in the extra directory
I don't know if I understand this line:
*) externals come first
it means before abstractions..
This order of searching makes sense to me:
- in local directory (dir of the patch)
- in the path
- in the extra directory
That way, you can stick deprecated objects into the local directory to make old patches work. But I have a question: do single objects before objects in libs, or vice versa?
libs are already loaded at startup, so they come first. I think if you load two libs with the same object, then the second one is valid .. have to check that ...
Greetings,
Guenter