Re: Aspect programming

[Adam Beneschan <adam@irvine.com>]

On 7/29/2011 9:09 AM, Anh Vo wrote:

>>> If you want it to apply to all units, you have to use it as a
>>> configuration pragma.
>>
>> It's not clear which one applies in the original poster's case.  If GNAT
>> does disallow more than one compilation unit per file, then clearly the
>> source in the original post must actually be multiple files (or else it
>> wouldn't have worked), and we weren't really told where the dividing
>> lines between the files are.  For all we know, the first
>> Assertion_Policy pragma could have been in its own file.
>
> Actually, each program unit is in a separate file per GNAT convention.
> While posting, I just copy and past their contents one after the
> other.

In that case, where was the Assertion_Policy pragma that you included at 
the top of your source?  In the same file as Aspect_Programming_Test, or 
in its own file?  If "file" == "compilation" on GNAT, then according to 
the language rules, if you included it in the same file (compilation) as 
the procedure, it would have applied only to the procedure.

However it's done, I believe that Assertion_Policy(Check) has to be 
applied to the specification of the Stacks generic package in order for 
you to get the checks to happen.  I don't know what works on GNAT or 
what doesn't.  But adding the pragma to the top of stacks.ads should 
work.  Compiling it as a configuration pragma that applies to "all 
future compilation_units compiled into the same environment" (10.1.5(8)) 
should work too, according to the language rules, but Martin's earlier 
comment seems to imply that it doesn't.

				-- Adam