why use two passes? Give GetOptions a sub to call instead. 

use Getopt::Long;
my (@foos, @bars, @bazen, @quuxi);
GetOptions (
    'foos=s'  => sub { shift; push @foos, split /,/, @_; },
    'bars=s'  => sub { shift; push @bars, split /,/, @_; },
    'bazen=s' => sub { shift; push @bazen, split /,/, @_; },
    'quuxi=s' => sub { shift; push @quuxi, split /,/, @_; },
);

[download]

of course, since your option names exactly match your arrays, something like this should work... 

use Getopt::Long;
my (@foos, @bars, @bazen, @quuxi);
sub setter {
   no strict refs;
   push @{shift}, split /,/, @_;
}
GetOptions (
    'foos=s'  => \setter,
    'bars=s'  => \setter,
    'bazen=s' => \setter,
    'quuxi=s' => \setter,
);

[download]

but at that point you should just use... 

use Getopt::Long;
my %opts;
sub setter {
   push @{$opts{shift}}, split /,/, @_;  
}
GetOptions (
    'foos=s'  => \setter,
    'bars=s'  => \setter,
    'bazen=s' => \setter,
    'quuxi=s' => \setter,
);

[download]

(All of that is completely untested ... I'm sure I have some syntax typos).

Update: Yeah, What Roy said....

In reply to Re: Getting Sparse - Taming Multivalued Options in Getopt::Long by hossman
in thread Getting Sparse - Taming Multivalued Options in Getopt::Long by Zaxo

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.