<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Gem #31: Preconditions/postconditions</title>
	<atom:link href="http://www.adacore.com/2008/04/14/gem-31/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adacore.com/2008/04/14/gem-31/</link>
	<description>AdaCore technology and news</description>
	<lastBuildDate>Mon, 06 Feb 2012 18:59:19 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Schwering</title>
		<link>http://www.adacore.com/2008/04/14/gem-31/comment-page-1/#comment-10390</link>
		<dc:creator>Chris Schwering</dc:creator>
		<pubDate>Fri, 04 Jun 2010 12:11:09 +0000</pubDate>
		<guid isPermaLink="false">http://www2.adacore.com/2008/04/14/gem-31/#comment-10390</guid>
		<description>I&#039;ve just replaced many assertions with pre-/postconditions in subprogram bodies; it&#039;s very handy, especially postconditions.
Wouldn&#039;t it be nice if we could place use-type-clauses before the pre-/postconditions to make operators usable in the conditions?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just replaced many assertions with pre-/postconditions in subprogram bodies; it&#8217;s very handy, especially postconditions.<br />
Wouldn&#8217;t it be nice if we could place use-type-clauses before the pre-/postconditions to make operators usable in the conditions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cyrille Comar</title>
		<link>http://www.adacore.com/2008/04/14/gem-31/comment-page-1/#comment-1380</link>
		<dc:creator>Cyrille Comar</dc:creator>
		<pubDate>Wed, 16 Apr 2008 17:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://www2.adacore.com/2008/04/14/gem-31/#comment-1380</guid>
		<description>Thanks for your nice comment Jeff. The issue of static vs dynamic pre/post conditions is indeed very interesting. Static analysis tools exploiting the information provided by the dynamic versions are already on their way... More on this later ;-) 
The static versions have been provided by tools such as Spark from Praxis for a while already.
Finding a way to marry the static &amp; the dynamic versions is an interesting challenge that we are considering seriously!</description>
		<content:encoded><![CDATA[<p>Thanks for your nice comment Jeff. The issue of static vs dynamic pre/post conditions is indeed very interesting. Static analysis tools exploiting the information provided by the dynamic versions are already on their way&#8230; More on this later ;-)<br />
The static versions have been provided by tools such as Spark from Praxis for a while already.<br />
Finding a way to marry the static &amp; the dynamic versions is an interesting challenge that we are considering seriously!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Creem</title>
		<link>http://www.adacore.com/2008/04/14/gem-31/comment-page-1/#comment-1379</link>
		<dc:creator>Jeff Creem</dc:creator>
		<pubDate>Wed, 16 Apr 2008 01:32:32 +0000</pubDate>
		<guid isPermaLink="false">http://www2.adacore.com/2008/04/14/gem-31/#comment-1379</guid>
		<description>Nice and interesting timing. I was just re-reading some of the old AIs in this area and thinking that I wish this had been implemented in Ada 2005.

One concern that had been expressed with the AIs was that in Ada we typically want static compile time checking and this only was seen as a dynamic check but hopefully tools like Polyspace and other static tools can begin to use this information. Even short of that, I like the idea of being able to use this to help document expectations.</description>
		<content:encoded><![CDATA[<p>Nice and interesting timing. I was just re-reading some of the old AIs in this area and thinking that I wish this had been implemented in Ada 2005.</p>
<p>One concern that had been expressed with the AIs was that in Ada we typically want static compile time checking and this only was seen as a dynamic check but hopefully tools like Polyspace and other static tools can begin to use this information. Even short of that, I like the idea of being able to use this to help document expectations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

