Hi morgon,

Elegance is in the eye of the beholder, I reckon. Personally I sometimes find it more elegant to decompose things into neat little units than to combine everything into one operation. 

use strict; use warnings; use feature 'say';
my $input = do { local $/; <DATA> };

my @output = map { /(\S+)$/ } grep { /SSID/ } split /\n/, $input;

say for @output;

__DATA__
BSS <blah blah>
   SSID: <ssid>
   <blah blah>
BSS <blah blah>
   SSID: <ssid2>
   <blah blah>
BSS <blah blah>
   SSID: <ssid3>
   <blah blah>

[download]
Output: 
$ perl 1182702.pl
<ssid>
<ssid2>
<ssid3>

[download]
Hope this helps!


The way forward always starts with a minimal test.

In reply to Re: more elegant way to parse this? by 1nickt
in thread more elegant way to parse this? by morgon

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.