Yes, I understand that I've gone from one extreme to the other on this subject. But to me, the connotation of a "Perl script" is something you can whip up in a few minutes, and it's difficult to hear about a complex program I've worked hard on for a long time being referred to in that way.
In a sense, all Perl programs are Perl scripts, and vice versa. I just prefer to say "program" because a "programming language" is generally taken more seriously than a "scripting language". That's just me.
-- Mike
--
just,my${.02} | [reply] |
Hm, I generally refer to a single .pl file as a perl "script", dozens (or hundreds) of these "scripts" together comprise an "application" or a "program". Of course you also have lots of packages and classes in there, but I've found that if I need to make these distinctions, I'm generally talking to a perl developer anyway, and all these trivialities are irrelevant by default. Just seems intuitive, I suppose I'm just used to it. Generally I don't care, the only thing that does irk me is saying that, for example, ASP somehow supercedes perl (or Perl); A little like saying that "UNIX was the operating system people used before Microsoft invented the GUI" :)
| [reply] |