Re^2: strange behavior of grep with global match

Thanks for the pointer to -Dr. I guess this is different from use re 'debug' as the latter works but I will have to recompile perl with -DDEBUGGING to try -Dr.

Pointers to any documentation that will help me understand the (I assume) non-trivial output that will be produced would be greatly appreciated. I know of perlreguts, though I'm not very familiar with it and will have to look again.

When the only tool you know is gdb everything looks like an object module, and your head hurts

Comment on Re^2: strange behavior of grep with global match

Replies are listed 'Best First'.
Re^3: strange behavior of grep with global match by jethro (Monsignor) on Aug 07, 2009 at 13:49 UTC
There seems to be not much difference between the output of the two. The advantage of re debug is that you can turn it on and off (with "no re 'debug';") inside the script to limit the output you are getting. Here is a diff between the output of the two debug methods on your program (without warnings,data::dumper, strict, as these produce output too): 1a2 > rarest char : at 9 6a8 > rarest char x at 2 11a14,17 > Omitting $` $& $' support. > > EXECUTING... > [download] As you can see there are only 4 non-empty lines different between the two	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: strange behavior of grep with global match
by jethro (Monsignor) on Aug 07, 2009 at 13:49 UTC

There seems to be not much difference between the output of the two. The advantage of re debug is that you can turn it on and off (with "no re 'debug';") inside the script to limit the output you are getting.

Here is a diff between the output of the two debug methods on your program (without warnings,data::dumper, strict, as these produce output too):

1a2
> rarest char : at 9
6a8
> rarest char x at 2
11a14,17
> Omitting $` $& $' support.
>
> EXECUTING...
>
[download]

As you can see there are only 4 non-empty lines different between the two

[reply]
[d/l]