[L2Ork-dev] Name clash

Jonathan Wilkes jon.w.wilkes at gmail.com
Tue Jul 14 22:06:18 EDT 2020

On Tue, Jul 14, 2020 at 4:45 PM Guillem Bartrina Moreno
<guillembartrina at gmail.com> wrote:
> Hi,
> it turns out that when you type an unloaded abstraction absolute path (/...path.../basename) in a text box to instantiate it, both methods 'basename' and '/...path.../basename' are added to pd_objectcreator object method list.
> This behaviour introduces a problem regarding the potential multiple abstractions with the same basename located in different paths.

That should happen for relative paths, too. [foo/bar]  should add both
"bar" and "foo/bar" as methods in the objectmaker.

> In the case the basename is one of the separate methods: bang, float, list, blob, ... either an error is thrown or the pd_objectcreator method with the same name is replaced.

Doesn't class_addmethod simply add another method by that name? My
understanding is that such a "bang" abstraction
(or external binary) is guaranteed to be added to the methodspace
*after* the built-in methods and therefore can never
be called (because any potential call will match the built-in "bang"
which has a lower index in the array of methods).


> How should we solve this?
> Best,
> --
> Guillem Bartrina Moreno
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev

More information about the L2Ork-dev mailing list