Jim Gibson writes:
[...]
>>
>> So doesn't it mean that inside find() the program is changing dir
>> right along with the search for executable files? That is, every time
>> the search digs a directory deeper, `stat' is called inside that
>> level.
>>
>> Isn't that the only way that '$_' would
Dear Andy Bach and Jim Gibson,
Thanks for your explanation and throwing light on the issue. It is greatly
appreciated.
best,
Shaji
---
Your talent is God's gift to you. What you do with it is your gift back to God.
---
I just wanted to give a big "Thank you" to all who responded to my
inquiry! This will help a lot in my search.
Thanks again,
Angela
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
On Fri, 4 Oct 2013 13:05:46 -0500
Andy Bach wrote:
> for a touch more flexibility
Try:
http://lookatperl.blogspot.ca/2013/07/a-look-at-conditional-compiling-of.html
--
Don't stop where the ink does.
Shawn
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional comman
On Thu, Oct 3, 2013 at 11:36 PM, Harry Putnam wrote:
> > Then I sprinkle print statements controlled by this variable throughout
> my program:
> >
> > print "\$_=$_\n" if $debug;
>
for a touch more flexibility, you can create your own debug levels
my $debug = 10;
...
print "in <> loop: \$_=$_\
Thanks, that works.
The only other gotcha I had (which took 5 seconds to figure out - just
for archival) was:
my $clen = length($color);
.
substr($line, $ereg->[0][$enum], 0, $color);
substr($line, ($ereg->[1][$enum] + $clen), 0, "\e[0m");
On Fri, Oct 4, 2013
On Fri, 4 Oct 2013 11:40:48 -0400
shawn wilson wrote:
> foreach my $ereg (@$match)
> {
> my $enum = ($#{$ereg->[0]} >= $#{$ereg->[1]} ?
> $#{$ereg->[0]} : $#{$ereg->[1]});
> print "ereg " . Dumper(@$ereg);
> print "blah " . $ereg->[0][0] . "\n";
> # Each match
> foreach my $i (0 .
On Oct 4, 2013, at 3:36 AM, Shaji Kalidasan wrote:
> Dear Perlers,
>
> I am trying to figure out the flow of a try catch block after executing the
> 'next' statement. In the try statement after illegal division by zero the
> program flow reaches catch block and then executes the 'next' stateme
I had to sleep on it and then the solution was stupidly obvious (as I
knew it would be).
However, now I'm having the problem I didn't think I would have - the
ANSI sequences are showing up as printable (as well as taking some
effect) in the print. However the escape that should turn the text
back
Dear Perlers,
I am trying to figure out the flow of a try catch block after executing the
'next' statement. In the try statement after illegal division by zero the
program flow reaches catch block and then executes the 'next' statement. After
executing the next statement the control flow has to
Hi!
I use the example at http://www.perlmonks.org/?node_id=553351 for
controlling a timeout of my threads (w/ perl 5.16.0).
In general this works great - but in rare occasions a thread is to be
killed milliseconds after it terminated regularly, resulting in a crash of
the whole script (which is
Thanks for your help.
-Vino.
On Fri, Oct 4, 2013 at 10:14 AM, Shlomi Fish wrote:
> Hi Vino,
>
> On Fri, 4 Oct 2013 09:12:20 +0530
> Frank Vino wrote:
>
> > Hi All,
> >
> >
> > Here is my request,
> >
> > I would like to hit my firewall with IP address and Domain users for 100
> > Users. I hav
12 matches
Mail list logo
