Thread: Is duplicate code always bad?

What would be wrong with copying F1 and pasting it as a starting point for F3?

Originally Posted by DarkFalz

What if copy paste wasn't available? Would it be worth keeping both?

What? Whether copying and pasting are available or not has nothing to do with repeating code.

Duplicate code is always bad, or at least a sign of a bad design. Why are you trying to argue for it?

If you want to continue this discussion, I highly suggest coming up with a concrete example with actual code instead of imagining scenarios. What if your space bar falls off? What if your electricity goes out?

If two methods are exact copies of each other then there's no reason to keep both. At the very least for legacy reasons one method could simply call the other one. This will make maintenance much easier.

However, just because two methods appear to take the same inputs and produce the same outputs doesn't necessarily mean they must arrive at the solution the same way. This is a good way to test out new solutions which may work better (i.e. looks cleaner, runs faster, or uses less memory). It's also entirely possible that both methods have their useful inputs. For example:

Consider the naive primality checker. It's quite inefficient, but for small numbers it's extremely fast. However, for larger numbers it's much quicker to check using a probabilistic primality checker. These methods have a larger overhead so it's not really great to use them with small numbers, but for larger numbers this overhead is significantly smaller than time spent performing useful computation. Different data structures are also a good example (e.g. linked lists vs. array lists).