Документация
HTML CSS PHP PERL другое

Section 4.1.  Defining a Subroutine

 
Previous
Table of Contents
Next

4.1. Defining a Subroutine

To define your own subroutine, use the keyword sub, the name of the subroutine (without the ampersand), and the indented block of code (in curly braces)[Section 4.1.  Defining a Subroutine] that makes up the body of the subroutine, something like this:

[Section 4.1.  Defining a Subroutine] Okay, purists, we admit that the curly braces are part of the block, properly speaking. And Perl doesn't require the indentation of the block, but your maintenance programmer will. So please be stylish.

    sub marine {
      $n += 1;  # Global variable $n

      print "Hello, sailor number $n!\n";
    }

Subroutine definitions can be anywhere in your program text, but programmers who come from a background of languages such as C or Pascal like to put them at the start of the file. Others may prefer to put them at the end of the file, so the main part of the program appears at the beginning. It's up to you. In any case, you don't normally need any kind of forward declaration.[*] Subroutine definitions are global; without some powerful trickiness, there are no private subroutines.[Section 4.1.  Defining a Subroutine] If you have two subroutine definitions with the same name, the second one overwrites the first one.[Section 4.1.  Defining a Subroutine] That's generally considered bad form or the sign of a confused maintenance programmer.

[*] Unless your subroutine is being particularly tricky and declares a "prototype," which dictates how a compiler will parse and interpret its invocation arguments. This is rare; see the perlsub manpage for more information.

[Section 4.1.  Defining a Subroutine] If you wish to be powerfully tricky, read the Perl documentation about coderefs stored in private (lexical) variables.

[Section 4.1.  Defining a Subroutine] A warnable offense, however.

As you may have noticed in the previous example, you may use any global variables within the subroutine body. In fact, all of the variables you've seen so far are globals; that is, they are accessible from every part of your program. This horrifies linguistic purists, but the Perl development team formed an angry mob with torches and ran them out of town years ago. You'll see how to make private variables in the section "Private Variables in Subroutines" later in this chapter.

    Previous
    Table of Contents
    Next
    © 2000- NIV