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 440683
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

A good Perl programmer is nowadays a programmer who knows her way around CPAN. This is an approach that is indeed harder at the start, but immensely more powerful in the long run.

Yes and no. Having that resource is great for developers, but a *massive* pain for distribution. It's no good having a nice 100-line perl script that requires a dozen CPAN modules to be installed before you can use it.

Especially when you then try to do so on some random UNIX platform, and find the module doesn't compile on that platform because of some subtle difference between Linux and (e.g) HP-UX.

Reply Parent Score: 2

Bill Shooter of Bul Member since:

Yeah, I've had to rewrite a few scripts to compensate for missing cpan modules.

Reply Parent Score: 2