SCIENTIFIC-LINUX-USERS Archives

December 2016

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
ToddAndMargo <[log in to unmask]>
Reply To:
ToddAndMargo <[log in to unmask]>
Date:
Fri, 30 Dec 2016 17:38:19 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
On 12/30/2016 05:32 PM, Steven Haigh wrote:
> On 31/12/16 10:01, ToddAndMargo wrote:
>> On 12/30/2016 01:14 AM, [log in to unmask] wrote:
>>> In conclusion
>>> Either one is good. Learn them both at least superficially. Tinker and
>>> play with them and see which one is right for you.
>> Perl's big advantage (over C) is that you can code twice as fast. The code
>> run twice as slow, but that is another issue.
>>
>> And, if you are a sloppy programmer, Perl is truly a "write only"
>> language.  It becomes impossible to maintain.
>>
>> I personally use Top Down that I learned with Pascal and Modula 2.
>> My Perl programs are easy to maintain.  Some Perl scripts I
>> have looked at, I just have to shake my head.  What in the world
>> is going on.  There is no enforcement of good programing
>> practices in Perl.
> I have to disagree with your last point. The programming language should
> never dictate programming practices. That is up to the programmer to do.
>
> Trying to solve a human problem like 'style' with technology is a
> failure from the start.
>
Pascal did force a lot on the programmer.  It did back fire.
And there is a lot of really miserable code out there.

It is not how fast you can code something.  It is how maintainable
it is afterwards.  Some folks refuse to write maintainable code.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ATOM RSS1 RSS2