Subclassing errors, OOP, and practically checkable rules to prevent them
<|reference_start|>Subclassing errors, OOP, and practically checkable rules to prevent them: This paper considers an example of Object-Oriented Programming (OOP) leading to subtle errors that break separation of interface and implementations. A comprehensive principle that guards against such errors is undecidable. The paper introduces a set of mechanically verifiable rules that prevent these insidious problems. Although the rules seem restrictive, they are powerful and expressive, as we show on several familiar examples. The rules contradict both the spirit and the letter of the OOP. The present examples as well as available theoretical and experimental results pose a question if OOP is conducive to software development at all.<|reference_end|>
@article{kiselyov2003subclassing,
    title={Subclassing errors, OOP, and practically checkable rules to prevent them},
    author={Oleg Kiselyov},
    journal={Proc. "Monterey Workshop 2001: Engineering Automation for Software
  Intensive System Integration," sponsored by ONR/AFOSR/ARO/DARPA. June 18-22,
  2001, Monterey, CA. -- pp. 33-42},
    year={2003},
    archivePrefix={arXiv},
    eprint={cs/0301032},
    primaryClass={cs.PL cs.SE}
}