but remember thats (dll_size * num_of_copies) memory you use up. for 1 dll with a couple of copies thats probably no big deal but i see alot of scripts with 5 or more dll's. Imagine each of them are loaded several times.
Double loading on purpose is one thing but accidentally should be avoided.
the real problem is in testing. if one of your testers has accidentally double loaded your dll it can cause problems. you might spend a week trying to figure out why one tester is having a problem and the other 10 arent. ive personally went back over hundreds of lines of code trying to find a problem that simply wasnt there (not in my code that is).
perhaps a new /dllcopy and $dllcopy command/ident would help. then you can load as many copies as you like. this way your doing it on purpose. no way to confuse wether its an accident or not. then all dll programmers need to do is mention wether or not /dllcopy will work with thier dll. likewise with $dllcall.
Last edited by Narusegawa_Naru; 11/01/05 08:49 PM.
