On Jan 9, 2006, at 1:41 PM, cdr wrote:
er, right... "A similar limitation exists for modules with the same name but residing in different directories. For example, if LoadLibrary is called on \Windows\Sample.dll, and then LoadLibrary is called on \MyDir\Sample.dll, \Windows\Sample.dll will simply be reloaded."
however, it gets even more insane:
"Two different modules cannot have the same file name, even if the extensions are different. These effectively have the same module name. For example, if LoadLibrary is made on Sample.cpl, the operating system will not load Sample.cpl, but instead will again load Sample.dll."
does this not mean hid.pd_losedows will still reload hid.dll instead? i guess you just can't win with Windows...
Yes indeed, this sounds like classic Microsoft. Arcane APIs and arbitrary limitations.
So it sounds like .cpl is a also a .dll, which would be another example of a special file extension for a shared lib. Hopefully the above rule only applies to Windows system files, like .cpl. Otherwise, I'm screwed!
I knew there was a good reason why I tried to avoid programming on Windows...
.hc
________________________________________________________________________ ____