http://www.perlmonks.org?node_id=1017437


in reply to Using grep in a scalar context

Are you maybe looking for something like this?

use v5.12; use List::Util qw(sum); my @dipept = qw( AABBCC AABBAA ); my $count = sum map { scalar(my @r = /AA/g) } @dipept; say $count;

(Outputs 3, because "AA" occurs three times in @dipept; once in the first string, twice in the second.)

package Cow { use Moo; has name => (is => 'lazy', default => sub { 'Mooington' }) } say Cow->new->name

Replies are listed 'Best First'.
Re^2: Using grep in a scalar context
by Anonymous Monk on Feb 07, 2013 at 10:35 UTC

    That expansive map statement is rather extravagant, given ...

    my $count = scalar map { /AA/g } @dipept;

    ... would produce the same result. Am I missing something?

      is rather extravagant ... would produce the same result. Am I missing something?

      Not really, although, a clarity argument could be made

      map is mostly used for generating lists, so sometimes it feels like the wrong tool for counting ( is the use of map in a void context deprecated ? , What's wrong with using grep or map in a void context? )

      tobyink improves clarity by generating a list of counts and adding/summing them (makes an array of matches, scalar array is count), map made a list, feels good :)

      you rely on generating a list of matches ( m//g) , and that map in scalar context returns a count

      Is there a performance advantage? Penalty? Was map-in-scalar as expensive as map-in-void (before perlv5.8.1)?
      It doesn't really matter as the reason for using map over foreach is clarity/brevity/tradition. The basic intent echoed in all the manuals and books, map for transforming lists, grep for filtering lists, foreach(for) for counting (iterating).

      Compare the "three"

      my @dipept = qw( AABBCC AABBAA ); use v5.12; use List::Util qw(sum); my $count1 = sum map { scalar(my @r = /AA/g) } @dipept; my $count2 = scalar map { /AA/g } @dipept; my $count3 = 0; $count3 += /AA/g for @dipept; my $count5 = 0; map { $count5 += /AA/g } @dipept; my $count6 = 0; grep { $count6 += /AA/g } @dipept;

      If you're thinking in terms of map and grep, thinking perlishly, then you write it like it makes the most sense to you, feels most natural, reads instantly and effortlessly (reads like breathing), needs no thought ...

      so what you're missing, is tobyink's brains

      I simply didn't think about doing it that way. I could probably count the number of times I've used map in a scalar context on my fingers.

      That said, given that the original question was about gene sequences, which can be pretty long strings, it seems preferable to avoid the creation of a temporary array containing all matches. Whether that's an important concern or not depends on many factors (typical number of matches expected; typical length of matched strings; etc).

      package Cow { use Moo; has name => (is => 'lazy', default => sub { 'Mooington' }) } say Cow->new->name