FAQ 1.13 Is it a Perl program or a Perl script?

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with Perl.


1.13: Is it a Perl program or a Perl script?

    Larry doesn't really care. He says (half in jest) that "a script is what
    you give the actors. A program is what you give the audience."

    Originally, a script was a canned sequence of normally interactive
    commands--that is, a chat script. Something like a UUCP or PPP chat
    script or an expect script fits the bill nicely, as do configuration
    scripts run by a program at its start up, such .cshrc or .ircrc, for
    example. Chat scripts were just drivers for existing programs, not
    stand-alone programs in their own right.

    A computer scientist will correctly explain that all programs are
    interpreted and that the only question is at what level. But if you ask
    this question of someone who isn't a computer scientist, they might tell
    you that a *program* has been compiled to physical machine code once and
    can then be run multiple times, whereas a *script* must be translated by
    a program each time it's used.

    Perl programs are (usually) neither strictly compiled nor strictly
    interpreted. They can be compiled to a byte-code form (something of a
    Perl virtual machine) or to completely different languages, like C or
    assembly language. You can't tell just by looking at it whether the
    source is destined for a pure interpreter, a parse-tree interpreter, a
    byte-code interpreter, or a native-code compiler, so it's hard to give a
    definitive answer here.

    Now that "script" and "scripting" are terms that have been seized by
    unscrupulous or unknowing marketeers for their own nefarious purposes,
    they have begun to take on strange and often pejorative meanings, like
    "non serious" or "not real programming". Consequently, some Perl
    programmers prefer to avoid them altogether.


Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short.  They represent an important
part of the Usenet tradition.  They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.

If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile.  If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.

Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release.  It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.

The perlfaq manual page contains the following copyright notice.


    Copyright (c) 1997-2002 Tom Christiansen and Nathan
    Torkington, and other contributors as noted. All rights

This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.

Site Timeline