Channels ▼


Your Favorite Automatic Data Endianness Conversion

AdaCore has expanded the scope of its code analysis and development portfolio with new versions of both CodePeer and the GNAT development environment.

More Insights

White Papers

More >>


More >>


More >>

Now moving to version 2.2, the CodePeer static analysis tool exists to help developers detect potential runtime and logic errors in Ada programs. New in this version are interfaces to Eclipse and spreadsheets. As well as additional HTML capabilities, the company says that this version is capable of handing requirements for the "highest levels of integrity and certification" — and this incorporates systems with large and complex code bases.

In line with the CodePeer update, GNAT Pro now moves to version 7.1 so that this development environment now supports an "increasingly wider" range of platforms and targets.

We are told that the "most striking" new feature of GNAT Pro 7.1 is support for automatic data endianness conversion — it's apparently already a customer favorite.

NOTE: IBM defines endianness as an attribute of a system that indicates whether integers are represented with the most significant byte stored at the lowest address (big endian) or at the highest address (little endian).

Returning to CodePeer 2.2, the product introduces integration into GNATbench (the GNAT Pro Ada plug-in for Eclipse and Wind River Systems Workbench), there is also full support for GNAT project files, message review from HTML reports, and a new "–level" switch to easily tune CodePeer messages and analysis time for any kind of code base.

"CodePeer 2.2 brings users an extra level of flexibility through interfaces to Eclipse, spreadsheets, and full HTML capabilities," said Arnaud Charlet, CodePeer product manager at AdaCore. "This new release now provides solutions for the full range of Ada projects, including those with requirements for the highest levels of integrity and certification, as well as systems with large and complex code bases."

Related Reading

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.