Christian Seberino wrote:
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?
Because you have no proof it will ever "get banged into shape".
Furthermore, since you are unlikely to have unit tests on the old code
(unit tested code rarely gets called spaghetti), you have no knowledge
of when it actually does get banged into shape.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
