<html><head></head><body>I'm pretty sure that there is only one "special" name that you need for a function and that is the setup entry point for the dynamic library that contains your external/externals, which is named after the file it's in. So, you could rename the setup function for the timbreID class because if your library calls it, it doesn't matter to PD what it is called. Then rename your whole library and it's setup entry point to timbreID, and then you should be able to have [timbreID/timbreID]<br><br>Alex<br><br><div class="gmail_quote">On August 2, 2019 6:29:44 AM PDT, William Brent <william.brent@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr">Maybe there's a trick someone can suggest, but I didn't think that was possible. There's a timbreID.c source file for the [timbreID] object in the library, and a timbreIDLib.c source file for building the whole library as a single binary. That calls the _setup() functions for all the individual objects and also has a timbreIDLib_setup function itself. So making the names the same would result in two timbreID_setup() calls that are supposed to do two different things. I never looked into ways to work around that...<div><br><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 1, 2019 at 4:42 PM Alexandre Torres Porres <<a href="mailto:porres@gmail.com">porres@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Em qui, 1 de ago de 2019 às 13:27, William Brent <<a href="mailto:william.brent@gmail.com" target="_blank">william.brent@gmail.com</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Alex, thanks for taking a look. Yes - the reason I ended up calling the single library binary timbreIDLib is that there was already a [timbreID] object in the library. I just wanted to avoid confusion. Looking back, I wish I had named that object something else. At this point I think I'd rather live with an awkwardly named library rather than change the name of any individual object within it, but I'm open to suggestions.</div></blockquote><div><br></div><div>My suggestion was to change the name of library, not the object. But I don't really understand the challenges involved (haven't really checked the code structure). Though I think it's feasible. What do you say? Have you considered it and thought it wasn't possible or worth it?</div><div><br></div><div>cheers</div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">William Brent<br><a href="http://www.williambrent.com" target="_blank">www.williambrent.com</a><br><br>“Great minds flock together”<br>Conflations: conversational idiom for the 21st century<br><br><a href="http://www.conflations.com" target="_blank">www.conflations.com</a></div>
</blockquote></div></body></html>