4 at 12:26 PM, Peter Holsberg wrote:
> Thank you. I will join the cygwin ML and ask there.
>
>
> On 3/8/2014 9:23 PM, Matt McAdory wrote:
>
>> This isn't a perl programming issue, but a cygwin/windoze environmental
>> execution issue. Please use the appropriate l
This isn't a perl programming issue, but a cygwin/windoze environmental
execution issue. Please use the appropriate list to seek further
assistance. http://cygwin.com/lists.html
http://cygwin.com/ml/cygwin/2004-07/msg00163.html
On Sat, Mar 8, 2014 at 6:25 PM, Yonghua Peng wrote:
> You may want
let me suggest you start here:
http://bit.ly/1lwoehv
and
http://www.catb.org/~esr/faqs/smart-questions.html
and then report back with specific questions or problems you are having.
Matt
===
*Clarke's Three Laws*
1. When a distinguished but elderly scientist states th
e, Jan 14, 2014 at 9:37 PM, Rob Dixon wrote:
> On 15/01/2014 03:09, Matt McAdory wrote:
>
>> Is there a method for determining the currently selected filehandle?
>> should I always check for undef and open my filehandle before writing to
>> it?
>>
>> u
Is there a method for determining the currently selected filehandle? should
I always check for undef and open my filehandle before writing to it?
use strict;
use warnings;
use autodie qw (:all);
use My:CustomMod_with_FH_write;
open (my $FH, ">", "filename.txt");
my $var = My:CustomMod_with_FH_w
I would hazard a guess that C:\Users\SHAJIK~1\.cpanm\work\1385391045
5000\build.log will hold the cookie crumbs you might be after.
after that I might look at
http://search.cpan.org/dist/Log-Log4perl/lib/Log/Log4perl/FAQ.pm#How_can_I_install_Log::Log4perl_on_Microsoft_Windows
?
and then ask log4pe
