Perl-Sensitive Sunglasses | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
This problem never happens with only one instance of the tool running, leading us to suspect concurrency issues (duh) From your description I suspect the same, but I might be wrong. DLLs should be shared objects, shouldn't they? What's around line 68 of XSLoader? Is Windows setting a lock on the DLL while opening it, then releasing the lock? That would be an explanation, but really bad behaviour also. eval seems the way to go, but not around the glob() calls - it should go around the use File::Glob call in a loop, retrying after a small amount of time and aborting after $count tries, since the DLL is bootstrapped upon loading the module AFAIK. sm<update> After seeing your post above, I'd sugges to try the BEGIN block trick to not defer the loading of File::Glob to the compiler. </update> --shmem
In reply to Re: Problems sometimes loading File::Glob
by shmem
|
|