map

Exactly what is in @emails, and what do you want to end up with? Be exact - is @emails an array of hashrefs or an array of arrayrefs or an array of strings or a table in a relational database? What is $email supposed to be? A string, a hash, an array of hashes, something else?

this might be useful.

Is @emails a list of lists, or is it a list of strings with some sort of delimiter between fields?

Assuming it's a list of lists:

foreach my $record ( @emails ) {
    my $email_address = $record->[1];
    # now do something with your email address.
}
[download]

Or maybe it's a list of strings with space-delimited fields (that's problematic):

foreach my $record ( @emails ) {
    if( $record =~ m/\S+\s+(\S+)/ ) {
        my $email_address = $1;
        # Do something with $email_address
    } else {
        die "Bad record format.\n";
}
[download]

That assumes that the name field contains only a single name, and that there are no spaces in the address field. Maybe it's more like this:

$record =~ m/(\S+\@\S+)$/
[download]

....which would ignore the first field, and simply look for the final field, which should contain no whitespace, and should include an '@'.

Email addresses are pretty hard to match accurately, but if your data set is fairly clean this should do the trick.

If you're using this to harvest email addresses for spamming, shame on you. But I'll give you the benefit of the doubt.

If I am not mistaken, I believe you want a "slice" of your data structure.

IMHO, one of the best discussions of complex data structures, and how to access their innards (using slices and so on), is to be found in Chapter 3. References and complex data structures of perlinter.pdf, available from Perl Training Australia. You'd probably want the most current version of the course notes, though, which have been reworked into progperl.pdf, available from the same page noted above.

HTH,

jdtoronto

my @emails = ({"id" => "1", "name" => "Foo", "email" => "me\@foo.com"}
+, {"id"=>"2", "name" => "Bar", "email" => "bar\@foo.com"}
);


foreach (@emails) {


  print $_->{"email"};

}
[download]

Often providing a little example script and some sample data makes a huge difference to how others perceive your question.

When you provide such a sample, where possible make it self contained with the fewest possible dependencies on non-core modules. Keep any data succinct, but make sure it encompases any important edge cases.