<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>AdaCore - The GNAT Pro Company &#187; Development Log</title>
	<atom:link href="http://libre.adacore.com/category/developers-center/development-log/feed/" rel="self" type="application/rss+xml" />
	<link>http://libre.adacore.com</link>
	<description>AdaCore technology and news</description>
	<lastBuildDate>Tue, 07 Feb 2012 12:00:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>[GNAT] Speed up gnatmake in presence of extending projects</title>
		<link>http://libre.adacore.com/2012/02/07/NF-71-L126-033-gnat/</link>
		<comments>http://libre.adacore.com/2012/02/07/NF-71-L126-033-gnat/#comments</comments>
		<pubDate>Tue, 07 Feb 2012 12:00:00 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[Development Log]]></category>
		<category><![CDATA[GNAT Compilation System]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[The check in gnatmake to verify if an object file is in the correct
object directory in the presence of extending projects has been optimized,
as it was taking a considerable amount of time when there were many sources.
]]></description>
			<content:encoded><![CDATA[The check in gnatmake to verify if an object file is in the correct
object directory in the presence of extending projects has been optimized,
as it was taking a considerable amount of time when there were many sources.
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/02/07/NF-71-L126-033-gnat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introducing CodePeer 2.1</title>
		<link>http://libre.adacore.com/2012/02/04/codepeer-2-1-webinar/</link>
		<comments>http://libre.adacore.com/2012/02/04/codepeer-2-1-webinar/#comments</comments>
		<pubDate>Sat, 04 Feb 2012 07:40:09 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[CodePeer]]></category>
		<category><![CDATA[Development Log]]></category>

		<guid isPermaLink="false">http://www2.adacore.com/?p=13811</guid>
		<description><![CDATA[
April 10, 2012 – 4:00pm GMT, 5:00pm CET, 11:00am EST



CodePeer is a source code analyzer that detects run-time and logic errors in Ada programs. This webinar, presented by Tucker Taft, will provide an overview of the technology, and focus on the new features introduced in this latest 2.1 release. These include support for Ada 2012 [...]]]></description>
			<content:encoded><![CDATA[
<p>April 10, 2012 – 4:00pm GMT, 5:00pm CET, 11:00am EST</p>



<p>CodePeer is a <a href="http://www.adacore.com/home/products/codepeer/">source code analyzer</a> that detects run-time and logic errors in Ada programs. This webinar, presented by Tucker Taft, will provide an overview of the technology, and focus on the new features introduced in this latest 2.1 release. These include support for Ada 2012 and its new syntax for specifying contracts, analysis of the elaboration of library units to enable detection of uninitialized global variables, better support for analysis of race conditions including new GPS reports, and more precise handling of preconditions and unused assignments. Presented by Tucker Taft, we will also allow for a Q&#038;A session at the end of the presentation.</p>


<p>To register, please visit:<br/>

<a href="http://www.adacore.com/home/products/codepeer/toolset/webinars/">http://www.adacore.com/home/products/codepeer/toolset/webinars/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/02/04/codepeer-2-1-webinar/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unit testing with GNATtest webinar</title>
		<link>http://libre.adacore.com/2012/02/04/gnattest-webinar/</link>
		<comments>http://libre.adacore.com/2012/02/04/gnattest-webinar/#comments</comments>
		<pubDate>Sat, 04 Feb 2012 07:35:38 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[Development Log]]></category>
		<category><![CDATA[GNATcoverage]]></category>

		<guid isPermaLink="false">http://www2.adacore.com/?p=13807</guid>
		<description><![CDATA[
March 20, 2012 – 4:00pm GMT, 5:00pm CET, 12:00am EST


The InSight webinar series continues with a webinar demonstrating how to write unit tests in a cost-effective way using the AdaCore toolset. More precisely it will show how to generate the unit testing framework using GNATtest, how to run the tests on an emulator such as [...]]]></description>
			<content:encoded><![CDATA[
<p>March 20, 2012 – 4:00pm GMT, 5:00pm CET, 12:00am EST</p>


<p>The InSight webinar series continues with a webinar demonstrating how to write unit tests in a cost-effective way using the AdaCore toolset. More precisely it will show how to generate the unit testing framework using GNATtest, how to run the tests on an emulator such as GNATemulator, and how to extract coverage results using GNATcoverage. This is primary aimed at developers and projects managers that already have unit testing infrastructure in place and are looking to reduce maintenance costs, as well as teams that are looking at implementing such techniques with minimal effort.</p>


<p>To register please visit:<br/>

<a href="http://www.adacore.com/home/products/gnatpro/webinars/">http://www.adacore.com/home/products/gnatpro/webinars/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/02/04/gnattest-webinar/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[IDE] GPS: Coverage Report accessible through Back button</title>
		<link>http://libre.adacore.com/2012/02/02/NF-52-G917-017-ide/</link>
		<comments>http://libre.adacore.com/2012/02/02/NF-52-G917-017-ide/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 12:00:00 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[Development Log]]></category>
		<category><![CDATA[GNATbench]]></category>
		<category><![CDATA[GPS]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[When clicking on a file or subprogram in the Code Coverage report, GPS open
this location in an editor, and it is now possible to click the &#34;Back&#34; button
in the toolbar to go back to the Code Coverage report.
]]></description>
			<content:encoded><![CDATA[When clicking on a file or subprogram in the Code Coverage report, GPS open
this location in an editor, and it is now possible to click the &quot;Back&quot; button
in the toolbar to go back to the Code Coverage report.
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/02/02/NF-52-G917-017-ide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[SPARK] Unmoded globals permitted with flow=auto</title>
		<link>http://libre.adacore.com/2012/02/01/NF-110-L113-038-spark/</link>
		<comments>http://libre.adacore.com/2012/02/01/NF-110-L113-038-spark/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 12:00:00 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[Development Log]]></category>
		<category><![CDATA[SPARK]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Previously, the Examiner enforced the rule that global annotations on
procedures must always specify variable modes when in automatic flow
analysis mode.  This rule has now been relaxed, so modes may be omitted
from globals if there is a derives annotation present. The Examiner will
then infer the modes from the derives annotation as it does in
information-flow mode. [...]]]></description>
			<content:encoded><![CDATA[Previously, the Examiner enforced the rule that global annotations on
procedures must always specify variable modes when in automatic flow
analysis mode.  This rule has now been relaxed, so modes may be omitted
from globals if there is a derives annotation present. The Examiner will
then infer the modes from the derives annotation as it does in
information-flow mode. This means that legacy code with derives annotations
and unmoded globals can be analysed with flow=auto.
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/02/01/NF-110-L113-038-spark/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[IDE] GPS: multi-line option in MDI.input_dialog</title>
		<link>http://libre.adacore.com/2012/02/01/NF-52-I527-048-ide/</link>
		<comments>http://libre.adacore.com/2012/02/01/NF-52-I527-048-ide/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 12:00:00 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[Development Log]]></category>
		<category><![CDATA[GNATbench]]></category>
		<category><![CDATA[GPS]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[The GPS function MDI.input_dialog used in plug-ins has been enhanced and
now offers multi-line input on fields as an option.
]]></description>
			<content:encoded><![CDATA[The GPS function MDI.input_dialog used in plug-ins has been enhanced and
now offers multi-line input on fields as an option.
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/02/01/NF-52-I527-048-ide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[PolyORB] Process ids in traces</title>
		<link>http://libre.adacore.com/2012/02/01/NF-29-L201-028-polyorb/</link>
		<comments>http://libre.adacore.com/2012/02/01/NF-29-L201-028-polyorb/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 12:00:00 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[Development Log]]></category>
		<category><![CDATA[PolyORB]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Process IDs can now optionally be included in trace messages logged to
standard error. This feature is enabled by setting &#34;pid=true&#34; in section
[log] of the PolyORB configuration.
]]></description>
			<content:encoded><![CDATA[Process IDs can now optionally be included in trace messages logged to
standard error. This feature is enabled by setting &quot;pid=true&quot; in section
[log] of the PolyORB configuration.
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/02/01/NF-29-L201-028-polyorb/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[GNAT] Debugger condition support in exception catchpoints</title>
		<link>http://libre.adacore.com/2012/01/31/NF-71-K516-013-gnat/</link>
		<comments>http://libre.adacore.com/2012/01/31/NF-71-K516-013-gnat/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 12:00:00 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[Development Log]]></category>
		<category><![CDATA[GNAT Compilation System]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[The debugger has been enhanced to support the use of conditions attached to
exception catchpoints.
]]></description>
			<content:encoded><![CDATA[The debugger has been enhanced to support the use of conditions attached to
exception catchpoints.
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/01/31/NF-71-K516-013-gnat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[GNAT] Avoid obsolescent feature messages for instances</title>
		<link>http://libre.adacore.com/2012/01/31/NF-71-L110-012-gnat/</link>
		<comments>http://libre.adacore.com/2012/01/31/NF-71-L110-012-gnat/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 12:00:00 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[Development Log]]></category>
		<category><![CDATA[GNAT Compilation System]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[When restriction No_Obsolescent_Features is used, the use of an obsolescent
feature in a generic template results in a diagnostic only when compiling
the template, and not when compiling instantiations of the generic.
]]></description>
			<content:encoded><![CDATA[When restriction No_Obsolescent_Features is used, the use of an obsolescent
feature in a generic template results in a diagnostic only when compiling
the template, and not when compiling instantiations of the generic.
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/01/31/NF-71-L110-012-gnat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[SPARK] Miscellaneous updates to Victor</title>
		<link>http://libre.adacore.com/2012/01/31/NF-110-L129-001-spark/</link>
		<comments>http://libre.adacore.com/2012/01/31/NF-110-L129-001-spark/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 12:00:00 +0000</pubDate>
		<dc:creator>AdaCore</dc:creator>
				<category><![CDATA[Development Log]]></category>
		<category><![CDATA[SPARK]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[We have fixed a number of small issues with victor wrapper: timing
information is now correctly stored in the .vct files; temporary
files are now correctly deleted; temporary files can be placed in
the current working directory and not deleted using the new -keep
flag; and finally, experimental support for CVC4 has been added.
]]></description>
			<content:encoded><![CDATA[We have fixed a number of small issues with victor wrapper: timing
information is now correctly stored in the .vct files; temporary
files are now correctly deleted; temporary files can be placed in
the current working directory and not deleted using the new -keep
flag; and finally, experimental support for CVC4 has been added.
]]></content:encoded>
			<wfw:commentRss>http://libre.adacore.com/2012/01/31/NF-110-L129-001-spark/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

