Why did you ignore the hint to avoid <pre>-Tags around your post?

Did you only think about the given code, or did you try it?

You also could have a look at Getopt::Long, which explains what happens, if an option doesn't have its optional argument...

Another possibility is something like this: 

#! /usr/bin/perl
# vim:ts=4 sw=4 sts=4 et nu fdc=3:
use strict;
use warnings;
use Getopt::Long;

my $x = "unset";

GetOptions(
    'x:s' => sub { $x = $_[1] ? $_[1] : 'true' },
) or exit 255;

print "$x\n";

[download]

It's up to you to refine the checks and values to fit your needs.

added: 

$ perl /tmp/getopt.pl 
unset
$ perl /tmp/getopt.pl -x
true
$ perl /tmp/getopt.pl -x foo
foo

[download]

In reply to Re^3: Wisdom on the Getopt::Long module by linuxer
in thread Wisdom on the Getopt::Long module by abhijithtk

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.