On Jun 21, 6:53 pm, jdoerr <jdo...@verizon.com> wrote:
> Hey, that's the question. I know Perl, so should I learn PHP? I've not
> yet read anything on php.net that tells me.
>
> Thank you,
> -jc

For me, it was syntax readability, I wanted to create programs that
read well. Perl (when I looked at sample code) had a lot of spaghetti
code in which made easy reading the tough.

larry@portcommodore.com wrote:
> On Jun 21, 6:53 pm, jdoerr <jdo...@verizon.com> wrote:
>> Hey, that's the question. I know Perl, so should I learn PHP? I've not
>> yet read anything on php.net that tells me.
>>
>> Thank you,
>> -jc
>
> For me, it was syntax readability, I wanted to create programs that
> read well. Perl (when I looked at sample code) had a lot of spaghetti
> code in which made easy reading the tough.
>
>

I wouldn't say that's typical of all Perl code. As with any language,
there are good programmers and poor programmers, and you can write
spaghetti code in any (or most, anyway :-) ).

I've seen some really good Perl code (and some really bad PHP code).

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

In article <1182574694.022848.143940@k79g2000hse.googlegroups .com>,
larry@portcommodore.com wrote:

> On Jun 21, 6:53 pm, jdoerr <jdo...@verizon.com> wrote:
> > Hey, that's the question. I know Perl, so should I learn PHP? I've not
> > yet read anything on php.net that tells me.
> >
> > Thank you,
> > -jc
>
> For me, it was syntax readability, I wanted to create programs that
> read well. Perl (when I looked at sample code) had a lot of spaghetti
> code in which made easy reading the tough.

Spaghetti one can work through. Its the unmemorable shortcuts like $_
and friends and the assumption that remembering all this rubbish somehow
makes you more cool.