Defensive Programming: Difference between revisions

From GM-RKB
Jump to navigation Jump to search
(ContinuousReplacement)
Tag: continuous replacement
(Redirected page to Defensive Programming Pattern)
Tag: New redirect
 
Line 1: Line 1:
 
#REDIRECT [[Defensive Programming Pattern]]
A [[Defensive Programming]] is a [[]] that ...
* <B>See:</B> [[Exception Handling]], [[Defensive Design]], [[Software]], [[High Availability]], [[Safety]], [[Computer Security]], [[Software Bug]], [[Source Code]], [[Code Audit]].
----
----
 
== References ==
 
=== 2020 ===
* (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/Defensive_programming Retrieved:2020-8-19.
** '''Defensive programming''' is a form of [[defensive design]] intended to ensure the continuing function of a piece of [[software]] under unforeseen circumstances. Defensive programming practices are often used where [[high availability]], [[safety]], or [[computer security|security]] is needed. <P> Defensive programming is an approach to improve software and source code, in terms of:
*** General quality – reducing the number of [[software bug]]s and problems.
*** Making the [[source code]] comprehensible – the source code should be readable and understandable so it is approved in a [[code audit]].
*** Making the software behave in a predictable manner despite unexpected inputs or user actions.
** Overly defensive programming, however, may safeguard against errors that will never be encountered, thus incurring run-time and maintenance costs. There is also a risk that code traps prevent too many [[Exception handling|exceptions]], potentially resulting in unnoticed, incorrect results.
 
----
[[Category:Concept]]
__NOTOC__

Latest revision as of 00:14, 19 August 2020