Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

I haven't done any old school mod_perl in a while, and I'm not sure if this is a coding style issue, global var issue or if I need to set something before implementing this or what...

There's a config module that loads configuration values and uses Exporter to expose $config in @EXPORT_OK. When I try to import it in a <Perl> block though, it throws an error. Here's the code (snipped)

<Perl> use XXX::Config qw($config); </Perl>

And the error I get is:

error (22)Invalid argument: <Perl>: Invalid command 'config', 
perhaps mis-spelled or defined by a module not included in the server

I'm not really sure where this issue is coming from. Anybody have any pointers?


In reply to using Exporter in <Perl> block in mod_perl by cLive ;-)

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.