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.
Thread beginning with comment 440757
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Why would I want to do it?
by sorpigal on Mon 13th Sep 2010 12:20 UTC in reply to "RE: Why would I want to do it?"
Member since:

All of these either exist in Perl, too, or don't aid the point: Maintainability.

Iterators and for comprehension are sweet sauce, sure, but once I have a stack of perl code that doesn't use them and works, what exactly is my motivation for porting to python?

A variety of implementations is nice, but does it *really matter* that I there's "only" one source base for perl? I mean, it's open source! It's not like there's a portability problem when the perl interpreter is concerned, it runs everywhere.

I could go on and on.

If you're *starting a new project* then some of your arguments are useful, but we're maintaining code in this article.

Although, in fact, even when starting a new project I would, personally, be prepared to defend Perl's advantages. I've seen far, far more cases, for example, where an interpreter point upgrade breaks python programs. But we

Reply Parent Score: 2