Sorry about the WordPress code mangling feature. If it makes it any better, it annoys the heck out of me too.

@Mark – neat golfing, and definitely better than my initial attempt I’m aiming for clearer rather than terser code (although terse is still important to compete with sed). Not sure if I got it.

@Sue -

I’ve tried to add back the missing angle-brackets. Let me know if I’ve missed any.

Ah yes, $var ||= 0 is a reflex to avoid undefined warnings when I have warnings turned on.

And I definitely like the way you’re going with S. My thinking was that sometimes the very next lines aren’t the interesting ones. Maybe you want the 2nd and 3rd lines following a particular match. It could be that doesn’t happen much in practice mind you.

Ah, HTML….

$lines ||= 0; serves no point, since the very next thing you do with $lines is check it for falsehood.

How about:

package S; # for "Sed"
use base 'Exporter';
our @EXPORT = ('p');
sub p # print ARG lines from stdin, starting with current
{
my $nlines = shift || return;
while (--$nlines) { print; $_ = <> ; }
print;
}

Then at the command line:

perl -MS -n '/somefunc()/ && p(3)'


How about:

package S; # for "Sed"
use base 'Exporter';
our @EXPORT = ('p');

sub p # print ARG lines from stdin, starting with current
{
my $nlines = shift || return;
while (--$nlines) { print; $_ = ; }
print;
}

Then at the command line:

perl -MS -n '/somefunc()/ && p(3)'


https://gist.github.com/847093