<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div id="ydp55010491yahoo_quoted_7811662831" class="ydp55010491yahoo_quoted">> On Sunday, May 12, 2019, 8:51:05 AM PDT, Christof Ressi <christof.ressi@gmx.at> wrote:
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;"><div><br></div>
<div>> anyway, I agree that ideally the structure of a library should be totally transparent to the user.
</div><div><div id="ydp55010491yiv5723940876"><div><div style="font-family:Verdana;font-size:12.0px;"><div><div> </div>
<div>>> Theoretically you could have a loader branch that would look for the "foo" binary in that case, load it, and then
<div>search for a "bar_setup" routine.</div>
<div> </div>
<div>> that's not a bad idea. doesn't seem too complicated to me. I might give it a shot.</div><div><br></div><div>I think what I'll do is to create a small external library in Purr Data to pentest the current myriad <br></div><div>functions for external loading. Then I'll make some coverage tests.</div><div><br></div><div>Once you get a solid patch set I'll plug it in and see if it breaks anything.</div><div><br></div><div>-Jonathan<br></div></div></div></div></div></div></div>
</div>
</div></div></body></html>