Don't call import because that only makes sense at compile-time. Call the binsearch function using its full name, and forcibly ignore its prototype...

SKIP: {
    eval { require List::BinarySearch }
        or skip "List::BinarySearch not installed", 2;

    $index = &List::BinarySearch::binsearch(
        sub {$a <=> $b},
        300,
        @num_array,
    );
    # ...
}

[download]

Alternatively, split the tests which use binsearch into a separate test file, and in that file use:

use Test::Requires "List::BinarySearch";

[download]

... which will automatically do the right thing in terms of skipping, importing at compile time, etc.

toby döt ink

In reply to Re: List::BinarySearch and conditional tests with Test::More by tobyink
in thread List::BinarySearch and conditional tests with Test::More by glasswalk3r

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.