use Perl

• what's really wrong with use_ok? (Score:1)

  by markjugg (792)

  I see the value of having a test script which reality-checks that everything compiles, especially if there are big gaps in a test suite.

  But I don't see what's wrong with "use_ok()" for a module that you neede to "use" anyway. It's hardly any more syntax. What's the harm?
  • Re: (Score:2)

    by Ovid (2709)

    First, here's the general 'correct' incantation:

    BEGIN {
        use_ok 'Some::Module' or die "Cannot use Some::Module";
    }

    If the module is not used in a "BEGIN" block, compile-time behavior is ignored (e.g., exported functions may alter how your code parses).

    If you don't have the 'or die' (or BAIL_OUT), things can get even worse. If the module fails to load, but most of it compiled, you can get partially compiled code loaded. Your 'use_ok' failure may scroll off the screen but failures show up much l
    • Re:what's really wrong with use_ok? summary (Score:1)

      by markjugg (792) <reversethis-{moc ... mus} {ta} {kram}> on 2008.11.06 11:34 (#65771) Homepage Journal

      So I would say it summarizes like this:

      If "use" a module it fails, the test grinds to a halt, which is nearly always a reasonable result.

      With "use_ok", the test may /continue/ causing unexpected results later on, because the module is not loaded, or worse, partially loaded.

      Thanks for your clarification, Ovid.

      Reply to This

      Parent