Re: Unsigned Integer Restraint Errors

["frikk" <frikker@gmail.com>]

On Mar 12, 2:11 pm, "frikk" <frik...@gmail.com> wrote:
> On Mar 12, 1:23 pm, "Adam Beneschan" <a...@irvine.com> wrote:
>
> > On Mar 12, 8:07 am, "frikk" <frik...@gmail.com> wrote:
>
> > > LASTLY:
> > > Please note that when I change the range value from 0 .. 5 to 0 ..
> > > 2**64-1, or 0 .. UNSIGNED_LONG_INT'Last, there is no constraint error
> > > raised. This is the same behavior as the first example.
>
> > I missed this question the first time.
> > [...]
>
> >                                   -- Adam
>
> Thanks for the answers Adam.  What you've said about the '-' makes
> sense. I'll look into this.
>
> The deal about how the constraint error being raised is outside the
> scope of the procedure makes sense as well. I'll update my code to
> reflect this.
>
> So if I compile with gnato - should this fix my constraint error
> raising? Basically I just need to be able to detect if the input is
> outside the range - without using something like "if x < 0 or x >
> 2**64 then" ...
>
> Thank you everyone!
> Blaine

As it turns out, the example that I've posted works just fine when I
use command line arguments:

b := UNSIGNED_LONG_INT'VALUE(Argument(2));

The constraint is thrown perfectly. I do this inside the procedure, of
course, not in the declarations.
Interesting eh?
Blaine