Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I usually only take care of code size...
(If I want to make my code more readable I use comment to describe what I'm saying)
Write your flat prog and then try to use subs instead of similar part of the code.
If using a sub reduce the number of lines it's often an obvious good choice.
(With experience you'll see that you'll do it at the design stage,
preventing you from writing more than needed...)

Now, I sometimes make sub from not-so-similar peaces of code
(using a added parampeters to achive sligltly different process on different data)
but it's not usually very good for the readablity.
I remember I wrote long ago a sub (which did and return severals (REALLY DIFFERENT)
things depending on the parameters, I saved some lines but it was an horror to read and debug...)

UPDATE :
Ooops I forgot to mention another important use for subroutines : I al so use them to make further modification easier.
I sometimes use sub when it doesn't really reduce my code size but when it enables me to modify the logical function at one place rather at thousand places in the code.


"Trying to be a SMART lamer" (thanx to Merlyn ;-)

In reply to Re: A question about the best way to use subroutines by arhuman
in thread A question about the best way to use subroutines by scottstef

Title:
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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others perusing the Monastery: (4)
As of 2024-03-29 14:28 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found