Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re^2: why perl doesnt recognize modules after copyied *.pm to paths in @INC

by czkzga (Initiate)
on Nov 29, 2012 at 14:06 UTC ( #1006258=note: print w/replies, xml ) Need Help??


in reply to Re: why perl doesnt recognize modules after copyied *.pm to paths in @INC
in thread why perl doesnt recognize modules after copyied *.pm to paths in @INC

yes that is right, i forgot about list of packages: Archive::Zip 1.28 or newer Class::MethodMaker 2.10 or newer UUID 0.03 or newer #Data::Dump 1.15 - successfully copied SOAP::Lite 0.710.08 or newer
  • Comment on Re^2: why perl doesnt recognize modules after copyied *.pm to paths in @INC

Replies are listed 'Best First'.
Re^3: why perl doesnt recognize modules after copyied *.pm to paths in @INC
by marto (Bishop) on Nov 29, 2012 at 14:11 UTC

    My advice stands, considering the number of dependant modules and external dependancies, for instance expat for XML::Parser, required by SOAP::Lite.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1006258]
help
Chatterbox?
[stevieb]: perldigious You should start by writing some unit tests. That'll ensure current functionality doesn't break with changes.
[choroba]: unit tests++
[choroba]: The only problem you can't solve by adding more tests is the problem of having too many tests.
[stevieb]: choroba Been there, done that :) Better too many than not enough though!
[stevieb]: I very often write a base set of unit tests before writing any code. It helps dictate the API, and ensures my earliest of ideas stay on track.

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (10)
As of 2017-07-21 20:03 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    I came, I saw, I ...
























    Results (335 votes). Check out past polls.