As the first step in the decommissioning of sasCommunity.org the site has been converted to read-only mode.
Here are some tips for How to share your SAS knowledge with your professional network.
I would take issue w/the definition of assertion here. To me, an assertion is an instruction to a compiler or runtime to throw an error if a particular condition is not true. They are a means of making your assumptions explicit.
I do not disagree with your definition. It is in line with that described by G.B. Nelson in his paper and my discussions w/him about the idea.
This is Being Proactive: why start the program if the input is not copacetic?
--macro maven 10:24, 18 May 2007 (EDT)
I added this page to Category:Testing, which has some pages that were clearly testing the wiki's capabilities, as well as pages about testing code. That category links to the empty Category:Assertions. I'm wondering if that's a useful category, or perhaps we'd want a Category:Test-Driven Development, which can include things like unit testing (a few papers in SAS use this) and is a big concept in software engineering across many languages. - paulkaefer (talk) 15:47, 15 June 2016 (CDT)
Paul, I agree. Test-Driven Development (TDD) is a key idea in understanding why these constructs are necessary. --Ronald_J._Fehd macro.maven == the radical programmer (talk) 07:35, 16 June 2016 (CDT)