perl qstn...

Randal L. Schwartz merlyn at stonehenge.com
Tue Apr 6 18:07:25 UTC 2010


>>>>> "Chuck" == Chuck Swiger <cswiger at mac.com> writes:

Chuck> Let's suppose you want to display one message if debugging is
Chuck> enabled, and a shorter message if it is not.

Then you wouldn't have used this construct.

>> If you don't like all this freedom, there's always Python. :)

Chuck> Yes, Perl lets you innovate a remarkable number of ways of
Chuck> solving the same problem using syntax that varies from clean and
Chuck> maintainable to constructs which even the original author won't
Chuck> understand without effort a few months later.  It seems to be
Chuck> uncommon for one to write unreadable Python code; I'm not sure
Chuck> additional freedom to write obfuscated code would be as
Chuck> beneficial as one may assume....

I call shenanigans: False dichotomy.

Perl has *many* options that are all clear and readable, and some
that aren't.  Python has a *few* options that are all clear and
readable, and some that aren't.

You may not appreciate that freedom.  Others do.  With freedom comes
responsibility.  If that's not for you, Perl's not for you.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn at stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion


More information about the freebsd-questions mailing list