Re: Suggestion for gnatstub

["Robert I. Eachus" <rieachus@attbi.com>]

Pascal Obry wrote:
> Not only limited types but with unconstraint types like String which is
> very common !

I used to have this problem until I realized a trick.  It shouldn't be 
necessary, but it works:

     function F(X, Y: Integer) return GNAT.Socket_Type is
        type Junk is access GNAT.Socket_Type;
        Junk_Reference: Junk;
     begin
       TBD("F(X, Y: Integer) return GNAT.Socket_Type");
       return Junk_Reference.all;
     end F;

The procedure TBD in package Incomplete normally prints a message:

     procedure TBD(S: in String) is
     begin Put_Line(S & " not yet implemented."); end TBD;

There are also a couple of useful functional forms returning Strings, 
Integers, Floats, and Booleans:

     function TBD(S: in String) return String is
     begin Put_Line(S & " not yet implemented."); return S; end TBD;

One of the reasons I like this approach is that any library unit body 
that is unfinished needs a "with Incomplete; use Incomplete;" to compile 
without errors...