Re: Help with a Cwd.pm build error

2006-01-25 Thread Randy W. Sims
Too tired to think properly, but... demerphq wrote: Also, something that would be really useful would be a way to force perl to close all files. Ie, to unload all dll's, close any intenral filehandles kept open for __DATA__ and __END__ etc. Then this batch file malarky would be totally

Re: Help with a Cwd.pm build error

2006-01-25 Thread demerphq
On 12/5/05, Randy W. Sims [EMAIL PROTECTED] wrote: demerphq wrote: (Regarding the problem of perl based installers not being able to install on WIn32 any file that the perl process itself has open during the build process. Such as .dll's and modules with unclosed __END__ or __DATA__ sections.)

Re: Help with a Cwd.pm build error

2006-01-25 Thread demerphq
On 1/25/06, Randy W. Sims [EMAIL PROTECTED] wrote: Too tired to think properly, but... demerphq wrote: Also, something that would be really useful would be a way to force perl to close all files. Ie, to unload all dll's, close any intenral filehandles kept open for __DATA__ and __END__