Re: Pragma Specs

[Sander van der Wal <svdwal@xs4all.nl>]

On Fri, 19 Apr 96 4:34:40 EDT acken@informatik.uni-kl.de (you) wrote:

> I added some minor corrections to pragma specs and decided to pass it
> round on the mailing list.
> 
> I'm especially interested in
> a) comments on loopholes in this document (ambiguous formulations,
>    missing specs, etc; anything you don't understand after reading the
>    whole text twice is definitely ambiguous), and
> b) answers to the open questions in the last paragraph.
> 
> [Open questions]

> The following predefined variables aren't part of the OOC front-end
> yet: 
> 
> StackCheck        -- how should this be marked in the GSA code?

I suggest as an attribute of the PROCEDURE/module body and the enter
instruction.

Definition:
<*StackCheck := TRUE *> 
  The runtime environment will check for stack overflows. On systems
  with software stack checking code will be generated to check
  for stack overflow.

<*StackCheck := FALSE *>
  The runtime environment will not check for stack overflows
  if this can be disabled, otherwise at compile time a warning 
  ('Cannot disable runtime stack checking') will be issued.
  On systems with software stack checks, no code to check
  stack overflow will be generated.
  
The default value of StackCheck is TRUE.


-- 
Sander        

We get to pick tools and equipment that suit the job.  We spend nearly all our 
time programming ART's computer's. (~P.J.Plauger: Programming on Purpose III)