It definitely irks me. In fact, in reaction to everything I write in Perl being called a "Perl script" regardless of its complexity, I have backlashed in the other direction. Around work, I always intentionally refer to code written in Perl as a "Perl program", even if it's a one-line throwaway script. The truth is that most Perl code I write is somewhere in between the two extremes of throwaway scripts and large applications, but a lot of people just don't understand that Perl is not merely for quickie one-off scripts.
-- Mike
--
just,my${.02} | [reply] |
| [reply] |
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] |
Yes, that irks me as well! I probably one of the few
people that didn't learn Perl from Web/CGI programming.
I use it for everything but web programming, just because
I don't do much(any) web design. I use Perl for client-
server programs, text processing, atomated processes, and
TONS of database work. I usally get to fustrated to reply
as well as people have here(Bravo to the monks who offered
some great definitions!), so I usally state,
"You can do anything with Perl!" :-)
STH
| [reply] |