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,803df5f3f60558d5
X-Google-Attributes: gid103376,public
From: stephenb@harlequin.co.uk (Stephen J Bevan)
Subject: Re: Uninitialized "out" parameters
Date: 1996/07/26
Message-ID: <STEPHENB.96Jul26101657@sorrol.harlqn.co.uk>#1/1
X-Deja-AN: 170237573
references: <31EEACDA.64880EEB@sage.inel.gov>
 <4t3f1u$t0u@newsbf02.news.aol.com>
organization: Harlequin Ltd, Manchester, UK
newsgroups: comp.lang.ada
Date: 1996-07-26T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <dewar.838165848@schonberg> dewar@cs.nyu.edu (Robert Dewar) writes:
   Of course there may be specialized architectures which make this kind of
   testing feasible, and of course you are certainly allowed to implement
   this in Ada 83 or Ada 95 (raising Program_Error as the result of failing
   the test), but it is interesting to note that there has been almost no
   demand for such implementations, since in the real world, the interest
   in performance and easy interface to the outside world would mean that
   these checks would almost always have to be suppressed.

I would have thought that the success of Purify shows that there is a
great demand for such tools in the C(++) world.  It isn't clear to me
why it should be any different for Ada.  I for one would be very
interested in using an Ada compiler that could *optionally* detect
references to uninitialised variables at runtime (and at compile time
where possible), until that time I'll carry on using GNAT (can't beat
it at the price :-).