Feh, I object to these sorts of false categorizations. Like some types of program are better or wors than others. It is hubris, false pride, and nothing more.

A program is code that performs a task or tasks in expressed or encoded form. The generic term.

A script is a program whos expressed and encoded form are the same, ala a program that is directly or indirectly interpreted.

An application is a program designed for continuous interaction or end-user use. In other words, a "seen" program designed for regular use. Compare application to utility, daemon, driver, and kernel.

You are talking about words on different axes. Program and code are the generics, where one tends to lean toward the expressed and the other to the post-processed forms. Script vs. Compilable or Interepreted vs. Compiled is one axis (and where Perl falls in that spectrum is rather hard to define). That axis is concerned with how the language works internally, a classification of design. The Application vs. Utility axis is concerned with how the program or programs are used. It is a classification of applicability and user needs.

Script has a deprecating sense in that most people perceive "scripts" as being linear, disposable programs that aren't created with serious code standards. I tend to call them scripts, even when they get past 10,000 lines and multiple design reviews and such simply because I am an engineer at heart and the emotional overtones of words are ignored by the (overly?) technical. If you find that "script" gets your code treated differently, start calling all of them "programs". =)

--
$you = new YOU;
honk() if $you->love(perl)