Sometimes it's worth asking Why?
I assume there would be no need to rewrite if the existing code did most
of what was needed. It may be easier to ask the customer what he really
wants rather than to re-engineer a crappy solution to an obsolete
problem.
--
http://mail.python.org/mailman/listinfo
Steven D'Aprano writes:
> On Sun, Jul 24, 2011 at 7:29 PM, Shashwat Anand
> wrote:
>
>> How do I start ?
>> The idea is to rewrite module by module.
>> But how to make sure code doesn't break ?
>
> By testing it.
>
> Read up on "test driven development".
>
> At this point, you have this:
>
> Per
Thanks everyone for the insight.
I got the idea as to how and where to start.
Guess I need to work in Perl for now, so as to start the conversion process.
Regarding Tests, I had already started writing tests before posting.
Writing tests for every module will be a pain as well as a nice experience.
On Sun, Jul 24, 2011 at 2:29 AM, Shashwat Anand wrote:
> I am working with a huge codebase of Perl.
> The code have zero documentation and zero unit-tests.
> It seems like a huge hack.
>
My condolences. Er, actually, it sounds kind of fun.
The underlying database schema is horrid.
> So I want t
On Sun, Jul 24, 2011 at 7:29 PM, Shashwat Anand
wrote:
> How do I start ?
> The idea is to rewrite module by module.
> But how to make sure code doesn't break ?
By testing it.
Read up on "test driven development".
At this point, you have this:
Perl modules: A, B, C, D
Python modules: none
Pyt
On Sun, Jul 24, 2011 at 7:29 PM, Shashwat Anand
wrote:
> How do I start ?
> The idea is to rewrite module by module.
> But how to make sure code doesn't break ?
> How can I import perl and python codes in each other ?
Can you separate the project into separate executables that call on
each other?
