I have two questions about the standard library:
1: from the manual
If a library function uses #Include, the working directory for #Include is the library function's own directory. This can be used to create a redirect to a larger library file that contains that function and others related to it.
Is this also true for DllCall? If I have a function and a dll used by that function in my library, do I need to call out the full path to the DLL (which I may not know), or will the function find it since it is in the same folder as the function, even though it may not be the working folder for the script?
2: from the manual
Although a library file generally contains only a single function of the same name as its filename, it may also contain private functions and subroutines that are called only by it. However, such functions should have fairly distinct names because they will still be in the global namespace; that is, they will be callable from anywhere in the script.
I think this may not be working right. Taking Titan's XPath.ahk as an example, I was trying to call both XPath() and XMLDoc() from my script without explicitly including the file. XPath() works as expected, but even though the file should have autoincluded itself for the XPath function, the XMLDoc function could not be found until I renamed it XPath_XMLDoc in both scripts. I assumed that this was because my code called XMLDoc before calling XPath, but changing the order did not seem to matter.
Does AHK build a list of functions it needs to find before including any? or does it include as it finds them?