"NULL" returned by a function

"NULL" returned by a function

[Victor Porton]

What if I want to make a function which returns either a value of type T or 
a value signifying "nothing" (like null pointer)?

To make things worse, T is a controlled type, so if we return just "access 
T" the finalization of the object of type T may be easily overlooked.

What is the best way to implement this? variant record? whatever?

Or maybe should I modify the type T to allow it contain "null" state? (In 
fact the particular T which I use can be easily modified to allow storing 
there null and checking whether it's state is null. But I think on the way 
not to be dependent on the ability to change the definition of T.)

-- 
Victor Porton - http://portonvictor.org

Re: "NULL" returned by a function

[Jeffrey Carter]

On 08/08/2014 02:10 PM, Victor Porton wrote:
> What if I want to make a function which returns either a value of type T or
> a value signifying "nothing" (like null pointer)?

Typically one should use a variant record with one variant for "nothing" and 
another for the value:

type Result (Has_Value : Boolean := False) is record
    case Has_Value is
    when False =>
       null;
    when True =>
       Value : T;
    end case;
end record;

-- 
Jeff Carter
"We call your door-opening request a silly thing."
Monty Python & the Holy Grail
17

Re: "NULL" returned by a function

[Victor Porton]

Jeffrey Carter wrote:

> On 08/08/2014 02:10 PM, Victor Porton wrote:
>> What if I want to make a function which returns either a value of type T
>> or a value signifying "nothing" (like null pointer)?
> 
> Typically one should use a variant record with one variant for "nothing"
> and another for the value:
> 
> type Result (Has_Value : Boolean := False) is record
>     case Has_Value is
>     when False =>
>        null;
>     when True =>
>        Value : T;
>     end case;
> end record;

But should I use a variant record EVEN IN THE CASE IF my data type T allows 
to store null values in it?

The benefit of using a variant record in this case that it makes the 
intention of the programmer more clear and thus increases readability and 
reliability. (It makes less like for a programmer to forget that a T value 
may hold a null access somewhere and this needs to be taken into account.)

The drawbacks are: longer source code and probably lower performance.

-- 
Victor Porton - http://portonvictor.org

Re: "NULL" returned by a function

[Jeffrey Carter]

On 08/08/2014 03:04 PM, Victor Porton wrote:
>
> But should I use a variant record EVEN IN THE CASE IF my data type T allows
> to store null values in it?

Probably not. But if you're writing Ada, and not pointer-heavy-language-in-Ada, 
then you're unlikely to be using access types.

-- 
Jeff Carter
"We call your door-opening request a silly thing."
Monty Python & the Holy Grail
17

Re: "NULL" returned by a function

[Victor Porton]

Jeffrey Carter wrote:

> On 08/08/2014 02:10 PM, Victor Porton wrote:
>> What if I want to make a function which returns either a value of type T
>> or a value signifying "nothing" (like null pointer)?
> 
> Typically one should use a variant record with one variant for "nothing"
> and another for the value:
> 
> type Result (Has_Value : Boolean := False) is record
>     case Has_Value is
>     when False =>
>        null;
>     when True =>
>        Value : T;
>     end case;
> end record;

   type String_Or_Null (Has_Value : Boolean := False) is
      record
         case Has_Value is
            when False => null;
            when True => Str: String;
         end case;
      end record;

rdf-auxilary.ads:22:31: unconstrained subtype in component declaration

What it the RIGHT (not just some) way of dealing with this case?

I can add to String_Or_Null additional discriminant "Length: Natural", but 
it is a superfluous information when Has_Value is False.

Finally I can make a private type (to hide the superfluous discriminant) 
from this. Good idea?

-- 
Victor Porton - http://portonvictor.org

Re: "NULL" returned by a function

[Jeffrey Carter]

On 08/09/2014 05:45 AM, Victor Porton wrote:
>
>     type String_Or_Null (Has_Value : Boolean := False) is
>        record
>           case Has_Value is
>              when False => null;
>              when True => Str: String;

    when True =>
       Value : Unbounded_String;

>           end case;
>        end record;

This assumes you need to distinguish between no string and the null string (""). 
Otherwise you can just return String.

-- 
Jeff Carter
"Insufficient laughter--that's grounds for divorce."
Play It Again, Sam
126

Re: "NULL" returned by a function

[Shark8]

On 08-Aug-14 15:10, Victor Porton wrote:
> What if I want to make a function which returns either a value of type T or
> a value signifying "nothing" (like null pointer)?

What's wrong with discriminated records?

Type Some_Container( Empty : Boolean ) is
   case Empty is
    When True  => Null;
    When False => Item : T;
   end case;
end record;

> To make things worse, T is a controlled type, so if we return just "access
> T" the finalization of the object of type T may be easily overlooked.

It seems that you're trying to program C/C++ in Ada, don't, that way 
lies only pain.

Re: "NULL" returned by a function

[Maciej Sobczak]

On Friday, August 8, 2014 11:10:28 PM UTC+2, Victor Porton wrote:

> What if I want to make a function which returns either a value of type T or 
> a value signifying "nothing" (like null pointer)?

The Ada.Containers.Indefinite_Holders package can be used to create a return type for such a function.

-- 
Maciej Sobczak * http://www.msobczak.com * http://www.inspirel.com