Ron Blaschke wrote:
Well, you've got a libparrot.dll. parrot.exe got to be linked against
it, and so have the dynclasses. Once parrot.exe runs, it pulls in
libparrot.dll. If a dynclass gets loaded, it also looks for its
missing symbols from libparrot.dll, and finds them in the already
loaded
Nick Glencross wrote:
> My understand is that on Windows DLLs must be self-contained and cannot
> have unreferenced symbols, and so I've linked against libparrot.so which
> of course pulls in much of its code. I see this also being done in the
> MSWin32 case...
Yes, Windows needs to know where the
