Assertion (software development): Difference between revisions

Content deleted Content added
External links: + John Regehr
m task, replaced: Annals of the History of Computing, IEEE → IEEE Annals of the History of Computing
Line 1:
{{About|the computer programming concept|assertions in the context of the [[Security Assertion Markup Language]] (SAML) open standard|Security Assertion Markup Language#Assertions}}
 
In [[computer programming]], an '''assertion''' is a [[Statement (computer science)|statement]] that a [[Predicate (mathematical logic)|predicate]] ([[Boolean-valued function]], i.e. a true–false [[Expression (computer science)|expression]]) is always true at that point in code execution. It can help a programmer read the code, help a compiler compile it, or help the program detect its own defects.
Line 180:
* ''[http://discovery.ucl.ac.uk/4991/1/4991.pdf A historical perspective on runtime assertion checking in software development]'' by Lori A. Clarke, David S. Rosenblum in: ACM SIGSOFT Software Engineering Notes 31(3):25-37, 2006
* ''[http://www.pgbovine.net/programming-with-asserts.htm The benefits of programming with assertions]'' by Philip Guo (Stanford University), 2008
* ''[http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1203056 Assertions: a personal perspective]'' by C.A.R. Hoare in: IEEE Annals of the History of Computing, IEEE, Volume: 25, Issue: 2 (2003), Page(s): 14 - 25
* ''[http://queue.acm.org/detail.cfm?id=2220317 My Compiler Does Not Understand Me]'' by Poul-Henning Kamp in: ACM Queue 10(5), May 2012
* ''[https://blog.regehr.org/archives/1091 Use of Assertions]'' by John Regehr