Re: Static assertions

["Marin David Condic" <marin.condic.auntie.spam@pacemicro.com>]

You have to be careful of the declarations. Just because you maybe did
something to declare (for example) a 16 bit integer type, doesn't mean that
'Size for the type won't end up as 32. Even if you use a rep clause, the
compiler doesn't have to honor it - although one would hope it was at least
polite enough to inform you of that fact.

Perhaps you could post the code you created to test it?

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"Jeffrey Carter" <jeffrey.carter@boeing.com> wrote in message
news:3B040DE4.468E779F@boeing.com...
> Jean-Pierre Rosen wrote:
> >
> > package Verifier is
> >    subtype Assert is Boolean range True..True;
> >
> >    Assert_1 : constant := Boolean'Pos( Assert (Integer'Size=32) );
> >    Assert_2 : constant := Boolean'Pos( Assert
> > (Integer'Size=4*Character'Size) );
> > end Verifier;
> >
> > (The Boolean'Pos serves to have a value used in a named number
declaration,
> > which requires a static context).
>
> Interesting. However, Rational Apex 2.4.6 on HP compiles this fine even
> if the declarations are changed to make the expressions false. A test
> program to output the values of Assert_X produces 2 zeros.
>
> If I change the declarations to
>
> Assert_1 : constant Assert := Integer'Size = 73;
>
> then the unit will not compile.
>
> --
> Jeffrey Carter