No eval, complies with strict: 
our ($user,$pass,$numb,$help);

my @cmdopt = (
   [qw(user u=s)],
   [qw(pass p=s)],
   [qw(numb n=i)],
   [qw(help h ?)],
);

GetOptions(map { +(join '|', @$_) => *{$main::{$_->[0]}}{SCALAR} } @cm
+dopt);

[download]
It will even bomb out if your variable and option names mismatch: 
Use of uninitialized value in ref-to-glob cast at t.pl line ##.
Can't use string ("") as a symbol ref while "strict refs" in use at t.pl line ##.
Of course, this assumes that the variables live in package main. If you need them elsewhere, the $main:: bit will need adjustment. It is possible to generalize even that bit, but that requires some painful twisting - or disabling the ref stricture.

Makeshifts last the longest.

In reply to Re^2: GetOpt::Long usage style by Aristotle
in thread GetOpt::Long usage style by demerphq

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, 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, 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.