in reply to code to replace

A script, to me, is a throw-away -- a quick and dirty solution (usually a one-liner) for an immediate problem ("Get me all XML files in this directory with ABCD in their name and rename them to *abcd*'.) A program is something that I am going to use more than twice. (Once is a script; twice is 'I did that last week....'; third time is A Tool in my ./tools directory.)

Seriously, the distinction used to be that Programs were compiled and linked, Scripts were interpreted. Then Perl and Java came along and changed the paradigm by having a two-pass Interpreter where the first pass generated Objects that the second pass executed. I use the terms almost interchangeably when I am talking to other Programmers/Developers. I always use 'Program' when I am talking to The Suits In Management.

----
I Go Back to Sleep, Now.

OGB

Replies are listed 'Best First'.
Re^2: perl script & perl program
by PyrexKidd (Monk) on May 03, 2010 at 04:53 UTC

    old_grey_Bear++!!!

    I use the terms almost interchangeably when I am talking to other Prog +rammers/Developers. I always use 'Program' when I am talking to The S +uits In Management.

    This IMHO have found is a rather major caveat in the business world. tell the suits you built a "Program" that makes you more efficient, you get a pat on the back and a raise. tell them you're writing a script and they give you funny looks and talk about you in their board meetings.