Timeline for inherited error replication?

Question

Due to inattentive curiosity, does anyone know the term for error replication in a new implementation of the old system in order to maintain backward compatibility with old clients that rely on buggy functionality? I would be particularly interested if this meant that you had to reverse engineer the wrong behavior in order to correctly reproduce what was not in the specification.

Answer 1

I think this is due to "backward compatibility".

A good example from Joel Spolsky, the famous " API War," about the development of Windows 3.1:

, Raymond, - , Windows , .

[...]

SimCity, , : , -, , DOS, Windows, , , . Windows , , , , SimCity . Windows, SimCity, , , , SimCity, , , .

Answer 2

" crapwards".

Answer 3

bug-for-bug-compatible.

Answer 4

I would agree to "error compatibility": it is too difficult to get all the errors.