>>One example that comes to mind is the failure of REPLACE when the current record pointer is at EOF(). IIRC that was a bug in Ashton-Tate dBASE III. Fox Software thought about fixing it, but
purposely continued that behaviour with FoxBASE, because their overarching design goal was 100%, ironclad compatibility with dBASE.
>
>A counterexample: DR-DOS was accused that some programs won't run on it. The response from Digital Research was "we didn't feel like emulating exactly ALL the bugs in MS-DOS, we felt it would be better to do it right".
Yep - sometimes the choice must be made, between compatibility, and correctness. It'll have an effect on the product's success.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
