I haven't had the opportunity to use Net::LDAP yet, so I will comment on the rest of the code.
Instead of printing line by line, why not use a here-doc for your usage message? Or use Pod::Usage and document your script in POD.
The following might make your defaults stand out more:
my ($user, $pass);
my $host = 'yourserver.yourdomain.com';
my $port = 389;
my $debug = 0;
GetOptions(
'h=s' => \$host,
'p=s' => \$port,
'u=s' => \$user,
'w=s' => \$pass,
'd+' => \$debug,
'q' => \&usage
);
Often, things like if ($debug ne 0) { ... } are better written as if ($debug) { ... }.
I would write debug and status messages to STDERR instead of STDOUT and include $0 (or similar) in error messages.
Hope this helps.
— Arien
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.