Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Is there merit in sub-dividing code into packages/subroutines even if it is not syntactically needed?

Surprisingly little is syntactically necessary. If you want to be pedantic, you really only need to fetch and store bits in memory and do a couple of comparisons.

The nice things about subroutines and packages is that they give you, the programmer, short names for things. You could write:

sub main { # read arguments ... # process arguments ... # open a file ... # process the file ... # open output file ... # write output file ... # clean up temporary files ... # exit }

That's a perfectly valid program. It might be the best program to write for your circumstance. It's nice that the comments are there. Look what happens when you use subroutines though:

sub main { my %args = read_arguments(); process_args( \%args ); my $file = open_file( \%args ); my $data = process_file( $file, \%args ); write_output( $data, \%args ); cleanup( $file, \%args ); }

The compiler doesn't care about the names. The computer really doesn't care about the names. They make quite a difference to me though.

I know which program I'd rather maintain.


In reply to Re: When Is Dividing Code Into Different Subroutines/Packages Important? by chromatic
in thread When Is Dividing Code Into Different Subroutines/Packages Important? by Missing Words

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 learning in the Monastery: (3)
As of 2024-04-25 06:18 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found