Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

Re: Is there any specific convention/best practices for perl module creation?

by eyepopslikeamosquito (Canon)
on Nov 17, 2012 at 23:09 UTC ( #1004358=note: print w/ replies, xml ) Need Help??


in reply to Is there any specific convention/best practices for perl module creation?

On what basis Directories and Files should be classified (Right now each of my Files are for handling specific section of our application)?
Focus not on files and directories, but on modules. The principal unit of decomposition in Perl is the module.

When designing modules, focus first on the module interface. Perl Best Practices, Chapter 17 (Modules), "Design the module's interface first" advises how to go about this (play testing and so on). For a detailed discussion of software interfaces in general, see On Interfaces and APIs.

What should be the maximum number of lines in a file?
Don't focus on lines in a file. Focus on sound software design. For example:
  • Design highly cohesive, loosely coupled modules.
  • Ensure modules can be tested in isolation.
  • Minimize the exposure of implementation details and avoid global data.
If you do that, code maintenance becomes easier, and none of your files should be grotesquely huge. See also:


Comment on Re: Is there any specific convention/best practices for perl module creation?

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1004358]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (7)
As of 2014-12-23 02:27 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (133 votes), past polls