The only way you are going to get around the syntax problems is to only compile the code in question if the module exists....

eval "use Foo::Bar"; eval <<"END" unless $@; sub my_method { # Code } END

but because that is going to introduce it's own problems, I would opt for moving that code into a module or a library...

eval "use Foo::Bar"; if ( $@ ) { require "have-foo-bar-library.pl"; } else { require "dont-have-foo-bar-library.pl"; }

As for the second part, because you are using eval BLOCK rather than eval STRING, the use will still be evaluated at compile time, rather than at run time. You could get the effect you are looking for by breaking the use up into it's components though...

eval { require Foo::Bar; import Foo::Bar; }

www.jasonkohles.com
We're not surrounded, we're in a target-rich environment!

In reply to Re: Conditional loading of methods by jasonk
in thread Conditional loading of methods by bruno

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.