More Resources
Recent Papers
Browse by Technology
Dev Log Archives
Developer Center |
|
AdaCore Development Log
Tuesday February 7, 2012
[GNAT] Speed up gnatmake in presence of extending projects »
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.
Posted in Development Log, GNAT Compilation System
Saturday February 4, 2012
Introducing CodePeer 2.1 »
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 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&A session at the end of the presentation.
To register, please visit:
http://www.adacore.com/home/products/codepeer/toolset/webinars/
Posted in CodePeer, Development Log
Saturday February 4, 2012
Unit testing with GNATtest webinar »
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 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.
To register please visit:
http://www.adacore.com/home/products/gnatpro/webinars/
Posted in Development Log, GNATcoverage
Thursday February 2, 2012
[IDE] GPS: Coverage Report accessible through Back button »
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 "Back" button in the toolbar to go back to the Code Coverage report.
Posted in Development Log, GNATbench, GPS
Wednesday February 1, 2012
[PolyORB] Process ids in traces »
Process IDs can now optionally be included in trace messages logged to standard error. This feature is enabled by setting "pid=true" in section [log] of the PolyORB configuration.
Posted in Development Log, PolyORB
Wednesday February 1, 2012
[IDE] GPS: multi-line option in MDI.input_dialog »
The GPS function MDI.input_dialog used in plug-ins has been enhanced and now offers multi-line input on fields as an option.
Posted in Development Log, GNATbench, GPS
Wednesday February 1, 2012
[SPARK] Unmoded globals permitted with flow=auto »
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.
Posted in Development Log, SPARK
Tuesday January 31, 2012
[SPARK] Automatic flow analysis mode is the default »
The default flow analysis mode is now automatic, which replaces the previous default of information flow. Automatic flow analysis was introduced in release 10. In this mode the Examiner selects information flow or data flow analysis on a per-subprogram basis depending on the presence or absence of derives annotations. This change is backwards compatible for current projects using information flow, data flow or a combination of the two. However, if you wish to enforce information flow or data flow for all analysis this can still be done explicitly via the option -flow=information or -flow=data.
Posted in Development Log, SPARK
Tuesday January 31, 2012
[SPARK] Miscellaneous updates to Victor »
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.
Posted in Development Log, SPARK
Tuesday January 31, 2012
[GNAT] Avoid obsolescent feature messages for instances »
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.
Posted in Development Log, GNAT Compilation System