Using your own Ada Standard Database

Sometimes it is helpful to parse code in context of its compilation environment rather than the environment defined as "Standard" in the Ada Language Reference Manual.

This is most often needed when your compiler vendor offers bindings to other languages or low level attributes of a chip or system.

The -standard option of undada offers support for using your compiler vendors Ada standard packages instead of Understand for Ada's.

To do so place all the source files containing the Ada specifications for the new standard in one directory. Then refer to this directory when creating a new database. It is important to note that this directory should be available at all times when parsing code.

Example - Using an alternate Standard Library

A common scenario is creating a library that contains the Ada Standard Library that ships with a specific compiler (e.g. GNAT, Greenhills, etc...).

In this example we will build a new standard Understand for Ada database containing a mythical compiler's Ada 95 standard library.

undada -create_95 -db myproject -standard /gnat/standard/

This tells Understand for Ada to use the files in /gnat/standard/ instead of it's usual Ada 95 standard library source.