On Thursday, May 2, 2002, at 02:39 , Paul Johnson wrote:
> On Thu, May 02, 2002 at 07:15:54PM -0000, Felix Geerinckx wrote:
>> on Thu, 02 May 2002 18:57:51 GMT, Tanton Gibbs wrote:
[..]
>> In the 3rd edition of the Camel, one reads in various
>> places:
>>
>> ...the Perl interpreter...
>>
>> Also see
>> perldoc -q perl
>> What's the difference between "perl" and "Perl"?
>
> So, Tanton has the correct idea, but didn't express it correctly. The
> Perl interpreter is perl. That is, perl is the interpreter for the Perl
> language.
p1: thanks for the lead to the 'perl v. Perl' portion of the pod -
but there is the semantical problem that 'awk' has a 'language'
just as 'sed' - and that one can do thing like
awk -f file_oh_stuff.awk
or
sed -f file_oh_stuff.sed
and few but the afficianado's would talk about 'Sed and Perl' -
in the sense of discussing the syntactical and lexical componentry
that forms their 'language' ....
p2: Ok - I'm probably being a bit 'orthodox' on the 'interpreter'
side of the game - since the classic 'shell interpreters' such as
/bin/sh
will not allow you to 'mess with' the file that is 'invoked' once
the execution of said file has begun... whereas perl actually does
a compilation of the 'Perl Language text file' into memory and one
can keep hacking away on the 'Perl Language text file' while the
'not-really-an-interpreter' 'perl' is out playing with the prior
instance of the foo.pl file.
p3: then there are the real 'cultural issues' between those people
who are merely 'scripting' in perl and those who are 'coding' in Perl.
made even funnier by various adverts for jobs where 'perl' is either
listed under 'and scripting languages like ...' or up in the 'coding
languages:...' section...
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
