Andrew Lentvorski wrote: > Is that more work than writing a new system by itself? Yes. By > definition you have to keep *2* code bodies correct simultaneously. > > However, at all points you have code which addresses all the user > demands that all *older* code also addressed.
But why is it so important to have the new code be at parity with old spaghetti code at all times? What's wrong with it being deficient for a while until it gets banged into shape? chris -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
