Re: What would be the Ada solution?

[mockturtle <framefritti@gmail.com>]

On Friday, February 4, 2011 5:33:57 PM UTC+1, KK6GM wrote:
> A colleague is working on some old code, written in C, that uses an
> "out of range" integer value to indicate no valid value.  Thus, a
> default value (in this case 0x7FFFFFFF) means no value has been
> entered.  All code that uses any values should check for this no-value
> and act accordingly, but of course not all the code actually does
> that, and there are odd cases where the no-value value gets processed
> as a valid value and then Bad Things Happen.
> 
> I'm curious what the Ada approach to this issue would be, the issue
> being to differentiate between valid and invalid values, and to catch
> (compile time or run time) any manipulation of an invalid value as if
> it were a valid value.

A solution that I saw used somewhere

   type Extended_Values is new integer range -1 .. 1023;
   subtype Valid_Values is Extended_Values range Extended_Values'first + 1 .. Extended_values'last;
 
   No_Value : constant Extended_Values := Extended_Values'first;

A variable that should always have a valid value is declared of type Valid_Values and you should get an exception when you try to assign No_Value to it.