ok, I don't see a problem here. the only symbol a Pd external exports (or should export) is the setup function - which is retrieved "manually" with GetProcAddress / dlsym. In theory all Pd externs could have the same setup function, at least on the platforms I know... Note that for example VST plugins all export the same entry point and it seems to work fine :-)

Gesendet: Sonntag, 12. Mai 2019 um 02:37 Uhr
Von: "Jonathan Wilkes" <jancsika@yahoo.com>
An: "Christof Ressi" <christof.ressi@gmx.at>
Cc: katja <katjavetter@gmail.com>, Pd-List <pd-list@lists.iem.at>
Betreff: Re: Aw: Re: [PD] Full stop '.' in class namespace

> On Saturday, May 11, 2019, 5:25:25 PM PDT, Christof Ressi <christof.ressi@gmx.at> wrote:

>> Does every supported PD platform allow you to a) dynamically load an object that defines
>> a previously defined symbol and b) search for a symbol starting from the last loaded
>> object and going up the dependency chain to the containing object?

> I'm not sure if I understand your question. are you talking about C symbols or Pd symbols here?

I'm talking about the system library on each OS responsible for dynamically loading

and searching objects into the running process. Like dlopen/dlsym

-Jonathan