Linked by Thom Holwerda on Fri 10th Sep 2010 14:59 UTC
General Development Python programmers shouldn't get too smug. While many people agree that Python is designed in a way that makes it a highly readable language, there can still be problems with legacy, untested Python code too. Porting legacy Perl to Python can be a daunting task. In this article, learn some of the theory behind dealing with legacy code, including what not to do.
Permalink for comment 441165
To read all comments associated with this story, please click here.
RE[3]: Why would I want to do it?
by sreque on Wed 15th Sep 2010 16:00 UTC in reply to "RE[2]: Why would I want to do it?"
Member since:

I know more about Perl than any other developer I've met, and I can hold my own against arguments from the likes of you just fine.

Also, there is a difference between languages like Lisp that give you a small core and let you easily build your own sub-language with macros, and a language like Perl where people have hackily built modules to cover up for past design mistakes. Perl's source transformer system, for instance, is inferior to anything the Lisp world has to offer. At the same time I've also heard Perl 6 improves significantly in this regard, but I won't hold my breath until Perl 6 is out and accepted by the community. Lastly, other scripting languages like Ruby also let you access and transform the AST, but this feature is not used nearly as much in these languages because, frankly, they don't need it nearly as badly as Perl does.

Anything else you'd like to try in defense of Perl? I promise you it is much easier to attack Perl than defend it!

Reply Parent Score: 1