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.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||