Quote:
Originally Posted by MysteryX
No problem.
1. Do a discovery of all DLLs and what's in them
2. Once the script is loaded and started rendering, unload everything that is not in use
NOTE: We still know what functions are available and where
3. If a function is later called that is unloaded, load it.
Otherwise, while we have any script playing that uses auto-loading, we cannot update any dll files.
|
I think this was actually the original Avisynth strategy. Mostly due to processes at the time being very limited in the number of simultaneous dlls that could be loaded so if you stuffed the autoload directory full you could actually encounter this problem.
Nowadays you can load a gazillion of dlls as long as you compile them with a shared runtime so there's really no reason to do things like that.