Talk:Assertions in design by contract: Difference between revisions
Talk:Assertions in design by contract (view source)
Revision as of 12:29, 1 October 2014
, 9 years agono edit summary
(Created page with "Asserts in C are supposed to check at runtime during development, as an aide to the programmer, but not be compiled into a release version. This behavior is often imitated by ...") |
No edit summary |
||
Line 41:
I have added an example of Ruby using [[https://github.com/egonSchiele/contracts.ruby contracts.ruby]]. Can we clarify which approach is required here. The Go solution, or any solution which just puts an if statement in a procedure named assert does not achieve either.--[[User:Nigel Galloway|Nigel Galloway]] ([[User talk:Nigel Galloway|talk]]) 12:20, 1 October 2014 (UTC)
:I hope we are going for DbyC. I shall look forward to the Racket solution "emphasizing that contract violations must blame the guilty party and must do so with an accurate explanation". Programmers will be taken out and shot!!!!--[[User:Nigel Galloway|Nigel Galloway]] ([[User talk:Nigel Galloway|talk]]) 12:29, 1 October 2014 (UTC)
| |||