<br><br><div class="gmail_quote">On Sat, Sep 25, 2010 at 10:31 AM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On 25 September 2010 20:17, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> On Unix systems using dlopen et al that's dlsym(RTLD_DEFAULT,symbolname). I don't know what the equivalent, if any, there is on Windows.<br>
><br>
<br>
</div>On Windows i'm using crtdll.dll , which is C-run-time dymanically<br>
loadable library.<br>
And unless VM compiled using different compiler (not GNU one), i am<br>
pretty sure that this name will remain same.<br>
And there is no 'global symbol namespace' concept in windows. You<br>
always should supply a distinct module handle (be it dll, or<br>
process module).<br></blockquote><div><br></div><div>So what should the abstraction be? </div><div>- a global space implemented directly by dlsym(RTLD_DEFAULT,...) on Unix and synthesized by enumerating al loaded modules on Windows</div>
<div>- provide a primitive that enumerates the loaded library names (using the standard lookup prims to search them)?</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
<br>
--<br>
</font><div><div></div><div class="h5">Best regards,<br>
Igor Stasenko AKA sig.<br>
</div></div></blockquote></div><br>