Getopt::Long has a configration option called 'gnu_compat' which I thought might work, but...
gnu_compat

gnu_compat controls whether --opt= is allowed, and what it should do. Without gnu_compat, --opt= gives an error. With gnu_compat, --opt= will give option opt and empty value. This is the way GNU getopt_long() does it.

Note that --opt value is still accepted, even though GNU getopt_long() doesn't.

Your problem is that note at the end. You do not want "--opt value" to be accepted, you want it to behave like "--opt= nextarg".

In the source for Getopt::Long there is this code to handle gnu_compat: 

# Check if there is an option argument available.
if ( $gnu_compat ) {
    my $optargtype = 0; # none, 1 = empty, 2 = nonempty, 3 = aux
    --cut--
    elsif ( defined $rest || @$argv > 0 ) {
        # GNU getopt_long() does not accept the (optional)
        # argument to be passed to the option without = sign.
        # We do, since not doing so breaks existing scripts.
        $optargtype = 3;
    }
    --cut--
    return (1, $opt, $ctl, $type eq 's' ? '' : 0)
        if $optargtype == 1;  # --foo=  -> return nothing
}

[download]
I think if you set '$optargtype' to 1 here it would work.

Maybe Getopt::Long could add a configuration option called 'gnu_compat_strict' so you could have: 

elsif ( defined $rest || @$argv > 0 ) {
    $optargtype = $gnu_compat_strict ? 1 : 3;
}

[download]

In reply to Re: Force Getopt::Long to Require ONLY Equals Sign Between Option Name and Value by tangent
in thread Force Getopt::Long to Require ONLY Equals Sign Between Option Name and Value by roho

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.