I have a third-party library that uses shell-style return codes (0 == success, anything else == error). An example chunk of code might be: 

my $libobj = Third::Party::Library->new(...);
my $item = $libobj->NewItem(...);
$item->frobinize(...) and die($libobj->GetErrorCode);
$item->blatinate(...) and die($libobj->GetErrorCode);

[download]

The ... and ... just does not seem very perlish. Are there other patterns that are more compact, perlish, and easy to maintain? It does seem as compact and readable as can be, but the ... and ... just seems wrong.

Any thoughts?

--MidLifeXis

In reply to Pattern for a shell-style call + error response by MidLifeXis

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.