Abstract
It all starts from the source. All large applications organize their source code into multiple separate directories, which we generally think of as modules. The source files themselves generally follow naming conventions so that we can easily find things. For instance, the traditional extension for Ada files (in GNAT) are .adb and .ads, although other technologies use other extensions (.1.ada, for instance). A lot of tools, in particular the compiler and the IDE, need to find source files in order to perform various actions on the code. Once they have found the sources, though, they also need to know how to manipulate them. For instance, the compiler might need to compile a specific file with style checks turned off, whereas all other files need style checks enabled, to ensure style consistency.
Recommendations
Gem #149: Asserting the truth, but (possibly) not the whole truth
Let's get started? In the beginning was created Ada. It did not have any assertions. Then came GNAT, which introduced pragma Assert. The ARG saw that it was good, and adopted it in Ada 2005. Then came GNAT again, which introduced pragma Precondition and ...
Gem #64: handling multiple-unit source files
This Gem describes how to compile applications in GNAT when source files contain multiple units. The preferred approach is to split source files, and here we describes how this can be done, although GNAT also provides a workaround that allows you to ...
Gem #151: Specifying Mathematical Properties of Programs
Let's get started? Integer overflows are exotic and dangerous beasts, that most programmers do not encounter very often, and tend to forget about. An integer overflow occurs when the result of an arithmetic computation does not fit in the machine ...






Comments