Michal 'vorner' Vaner wrote:
On Tue, Feb 20, 2007 at 08:05:12AM +1100, Daniel Noll wrote:
Think of the guy who has to maintain the code, too. Nothing sucks more than
trying to find bugs in C++ code. (Even C is easier...)
Maybe except finding a bug in perl :D That is what I call expressive
language (I have to learn that properly one day)
But I think we are getting OT a little bit…
I realize this is OT too, but I had to butt in :) You're parroting (sic)
the running joke about Perl, but if you always use strict, use warnings
and scope your variables as tightly as you can, debugging is not hard at
all.
Perl's 'problem' is that as well as being able to write clean, well
thought out code, it's just as easy to write a mess. Java, for example,
forces a lot more rules on you, and it has real OO, so mistakes that can
easily be made in Perl just can't be made in Java.
Yes, if you're debugging bad Perl, it can be hell. But, if you have to
do that and follow the cleanup rules, it's not impossible.
http://www.extremeperl.org/bk/refactoring
But then again, I may be biased :)
cLive ;-)
--
Perl Enveloper
Fonality.com
(877)366-2588 x7095
