You could subclass the library and convert the status codes: 
#!/usr/bin/perl
use strict; use warnings;

package Third::Party::Library::Call; 

use base 'Third::Party::Library';

foreach my $method (qw/bazinate barify/) {
    no strict 'refs';

    my $subref = __PACKAGE__->can($method)
            || die "Unknown method: $method";

    *$method = sub {my $stat = &$subref(@_);
                    return !$stat;
        };
}

[download]
Then things do look a little more perlish: 
my $libobj =  Third::Party::Library::Call->newObj;
$libobj->bazinate or die $libobj->GetErrorCode;

[download]

In reply to Re: Pattern for a shell-style call + error response by snoopy
in thread 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.