Abstract
By June 1949 people had begun to realize that it was not so easy to get a program right as had one time appeared. I well remember when I was trying to get working my first non-trivial program [in assembler code or perhaps machine language]. The realization came over me with full force that a good part of the remainder of my life was going to be spent in finding errors in my own programs. Turing had evidently realized this too, for he spoke at the conference on “checking a large routine.”—Maurice Wilkes (Turing Award winner, 1967), Memoirs of a Computer Pioneer (MIT, 1985), page 145.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
Placing too many error traps in a function can obscure what the function is supposed to do. In that case, sometimes, the traps should be moved into their own function.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2018 Michael Stueben
About this chapter
Cite this chapter
Stueben, M. (2018). Defensive Programming. In: Good Habits for Great Coding. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-3459-4_11
Download citation
DOI: https://doi.org/10.1007/978-1-4842-3459-4_11
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-3458-7
Online ISBN: 978-1-4842-3459-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)