I'm asking if was anything in the settings to make it work differently.

Yes. If you don't want pass_through's behaviour, don't use pass_through. 

use Getopt::Long (); 

our $opt_float;

Getopt::Long::Configure('no_auto_abbrev');
Getopt::Long::GetOptions('float=f')
   or die("Bad args\n");

print("\$opt_float = ", defined($opt_float) ? $opt_float : "[undef]", 
+"\n");
print("\@ARGV      = ", join(' ', @ARGV), "\n");

[download]

outputs 

>perl 551404.pl -float 1.3
$opt_float = 1.3
@ARGV      =

>perl 551404.pl -float abc
Value "abc" invalid for option float (real number expected)
Bad args

[download]

In reply to Re^4: Issues w/ getOptions parsing options with pass_through enabled by ikegami
in thread Issues w/ getOptions parsing options with pass_through enabled by Brawny1

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.