On Sunday, May 12, 2019, 8:51:05 AM PDT, Christof Ressi christof.ressi@gmx.at wrote: anyway, I agree that ideally the structure of a library should be totally transparent to the user. >> Theoretically you could have a loader branch that would look for the "foo" binary in that case, load it, and then search for a "bar_setup" routine. > that's not a bad idea. doesn't seem too complicated to me. I might give it a shot.
I think what I'll do is to create a small external library in Purr Data to pentest the current myriad functions for external loading. Then I'll make some coverage tests. Once you get a solid patch set I'll plug it in and see if it breaks anything. -Jonathan