From: Gerhard Radatz <gerhard.radatz@aut.alcatel.at>
Subject: Re: Finding out parameters which are not written
Date: 1997/08/12
Date: 1997-08-12T00:00:00+00:00 [thread overview]
Message-ID: <33F07EA1.51D1@aut.alcatel.at> (raw)
In-Reply-To: 33F02867.322D@aut.alcatel.at
Gerhard Radatz wrote:
>
> Does anyone know about a tool which can detect such situations as the
> following:
>
> procedure xxx (result: out INTEGER) is
> begin
> if <<condition>> then
> result := 0;
> end if;
> end;
>
> Obviously, this proc is erroneous and result will not be written if
> <<condition>> is FALSE.
> However, my Ada-Compiler (DEC-ADA for VMS) does not detect this problem,
> because result is written "at least once" in the body of xxx.
>
> Is there any tool which can provide help ???
I admit that it is very difficult to find such potential problems at
compile time. Therefore, I'm rather looking for such a thing like an
expert system which can examine complex code, evaluate every possible
flow of control and at least give some hints.
Surely its best to code-read to be able to find out unwritten
parameters, but in projects consisting of a few hundred packages with a
few 100.000 lines of code, this is lots of work.
next prev parent reply other threads:[~1997-08-12 0:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-12 0:00 Finding out parameters which are not written Gerhard Radatz
1997-08-12 0:00 ` Gerhard Radatz [this message]
1997-08-12 0:00 ` Robert A Duff
1997-08-12 0:00 ` Matthew Heaney
1997-08-12 0:00 ` Larry Kilgallen
1997-08-17 0:00 ` Fergus Henderson
[not found] ` <5u180q$l69@mulga.cs.mu.OZ.AU>
1997-08-28 0:00 ` Stuart Palin
-- strict thread matches above, loose matches on Subject: below --
1997-08-27 0:00 Robert Dewar
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox