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,d57302f2954365e1
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Question about base types
Date: 1997/02/10
Message-ID: <dewar.855570988@merv>#1/1
X-Deja-AN: 217776827
references: <mheaney-ya023280002601971414080001@news.ni.net>
 <E4oE3q.1tq@world.std.com> 	<mheaney-ya023280003001970055250001@news.ni.net>
 <EACHUS.97Feb3221558@spectre.mitre.org> <dewar.855063927@merv>
 <32FB45D4.2160@watson.ibm.com>
organization: New York University
newsgroups: comp.lang.ada
Date: 1997-02-10T00:00:00+00:00
List-Id: <comp.lang.ada>


Norman suggested:

<<So impressive, in fact, that I'm going to raise the bar:  Do you issue
the same warning for unintentionally recursive controlled-type
operations?  (For a controlled type CT, these would include a version of
Initialize that creates an uninitialized object of type CT, a version of
Adjust that assigns an object of type CT, or a version of Finalize in
which an object of type CT goes out of existence, either because it was
declared in finalize, because it was uncheckedly deallocated in
Finalize, or because it was created by an allocator for an access type
declared in Finalize.)

Such cases are especially hard to diagnose because the unintentional
recursive call is implicit, i.e., you won't find it in the program text.>>


Robert replies

At least some cases of this kind are caught:

     1.    with Ada.Finalization; use Ada.Finalization;
     2.    package a is
     3.       type m is new controlled with null record;
     4.       procedure Initialize (Object : in out m);
     5.    end a;

     1.    package body a is
     2.       procedure Initialize (Object : in out m) is
     3.          x : m;
                 |
        >>> warning: infinite recursion
        >>> warning: Storage_Error will be raised at runtime

     4.       begin
     5.          null;
     6.       end;
     7.    end a;

The diagnostic here is a little mysterious, but I would hesitate to
special case it unless someone really has run into this in practice.
Generally we like to apply the reality check of someone actually
(a) running into an error that could be caught and (b) being
mystified enough to waste time looking for the error. I always
hesitate to add new diagnostics that come only from thought
experiments.

Note that we are happy to get suggestions for error checks and improved
diagnostics. The best form for such suggestions is to send a complete
source program to report@gnat.com with a suggestion of exactly what
error message you would like to see. Now sometimes, such suggestions
amount to asking the compiler to read your mind, and it is impossible
to implement them, but it is remarkable how often we *have* been able
to sort things out, even in cases which at first look very hard.

Robert Dewar
Ada Core Technologies