From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,cd5c71f09395807a
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Assertions in Ada
Date: 1997/08/25
Message-ID: <dewar.872559855@merv>#1/1
X-Deja-AN: 268527838
References: <EFBI6M.F2K.0.-s@inmet.camb.inmet.com>
 <199708251351.PAA13197@basement.replay.com>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-08-25T00:00:00+00:00
List-Id: <comp.lang.ada>


Jeff said

<<another post by R. Dewar. The package provides checking even with
compilers that don't support pragma Assert. The advantage of the pragma
is that you can use it in a declarative region, where a procedure call
is not allowed. I considered also providing a function for use in
declarative regions, but didn't, because I expect optimization to
eliminate the unused constants I would declare with the function.>>


The constants could be eliminated, but not their initializing expressions
if they have potential side effects, which the assert call most surely
does, so your fear of being done in by the optimizer here is groundless.

Incidentally, GNAT also provides pragma Debug:

  pragma Debug (procedure-call-statement);

which is a procedure call that can be turned on or off by an external
compiler switch, and which can occur in a declarative region. This
allows more general processing than the assert pragma.