Next Next

Gem #24: Null Considered Harmful (Part 2—Efficiency)

Let's get started…

In last week's gem, we talked about the documentation advantages of using "not null". Here's another example, first with null:

   procedure Iterate
     (T : Table; 
      Action : access procedure (X : not null Ref_Element)
                                      := null);
   --  If Action is null, do nothing.

...and without null:

   procedure Do_Nothing (X : not null Ref_Element) is null;
   procedure Iterate
     (T : Table; 
      Action : not null access procedure (X : not null Ref_Element)
                                      := Do_Nothing'Access);

I much prefer the style of the second Iterate.

The "not null access procedure" is quite a mouthful, but it's worthwhile, and anyway, the compatibility requirement for Ada 2005 requires that the "not null" be explicit, rather than the other way around.

Another advantage of "not null" over comments is for efficiency. For example:

   procedure P (X : not null Ref_Element) is
      X.all.Component := X.all.Component + 1;
   end P;

   procedure Q (X : not null Ref_Element) is
      while ... loop
         P (X);
      end loop;
   end Q;

   procedure R is
      Q (An_Element'Access);
   end R;

Without "not null", the generated code for P will do a check that X /= null, which may be costly on some systems. P is called in a loop, so this check will likely occur many times. With "not null", the check is pushed to the call site. Pushing checks to the call site is usually beneficial because (1) the check might be hoisted out of a loop by the optimizer, or (2) the check might be eliminated altogether, as in the example above, where the compiler knows that An_Element'Access cannot be null.

This is analogous to the situation in Ada 95 with other run-time checks, such as array bounds checks:

   type My_Index is range 1..10;
   type My_Array is array (My_Index) of Integer;

   procedure Process_Array (X : in out My_Array; Index : My_Index);

If "X (Index)" occurs inside Process_Array, there is no need to check that Index is in range, because the check is pushed to the caller.

Related Source Code

Ada Gems example files are distributed by AdaCore and may be used or modified for any purpose without restrictions.

Attached Files

Bob Duff




Comments on Gems are now closed.