> Have Scripts track their associated primInfoDef (if any). In turn, > the primInfoDef for a module now tracks its corresponding DLL > handle. > This is all done so that upon unloading a script, we can properly > let go of the underlying DLL (and primInfoDef.) Excellent! A