From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20452 invoked by alias); 25 Jun 2007 20:47:14 -0000 Received: (qmail 20442 invoked by uid 22791); 25 Jun 2007 20:47:13 -0000 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 25 Jun 2007 20:47:10 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id CA0C32A9B9D; Mon, 25 Jun 2007 16:47:08 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id g7oDmoKbGGkC; Mon, 25 Jun 2007 16:47:08 -0400 (EDT) Received: from [127.0.0.1] (nile.gnat.com [205.232.38.5]) by rock.gnat.com (Postfix) with ESMTP id 7DF372A9ABE; Mon, 25 Jun 2007 16:47:08 -0400 (EDT) Message-ID: <468029CC.6080002@adacore.com> Date: Mon, 25 Jun 2007 20:47:00 -0000 From: Robert Dewar User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: Robert Dewar CC: Michael Eager , Paul Koning , jimb@codesourcery.com, stanshebs@earthlink.net, gdb@sources.redhat.com Subject: Re: What's an annex? stratum? References: <467D5FEF.7010900@eagercon.com> <467D6D1F.7090507@earthlink.net> <467D6FB8.4080909@eagercon.com> <468009EA.4040504@eagercon.com> <18048.5444.903092.843811@pkoning.equallogic.com> <20070625193135.GA6391@caradoc.them.org> <4680199F.7020906@adacore.com> <18048.7178.168032.6683@pkoning.equallogic.com> <46802100.6050600@eagercon.com> <4680284E.5010406@adacore.com> In-Reply-To: <4680284E.5010406@adacore.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-06/txt/msg00271.txt.bz2 Robert Dewar wrote: > Michael Eager wrote: > > >> Internals documentation provides a guide through the program in >> some kind of logical order. It's difficult to provide that order >> at the file or function scope. > > Well the sources can provide a clear logical order, > e.g. the child hierarchy and the separate specs and bodies in an > Ada program. Anyway, see the GNAT front end, where by policy there > are NO separate design documents, for an indication of what I > consider ideal, or almost ideal (probably one short page of the > form .. start here, then ... would be helpful). For instance, I am not sure there is anywhere in the front end that says that par-chx is the parser routines for chapter x constructs in the RM, and sem_chx is the semantics routines. One thing that helps in the case of Ada is that everyone is familiar with the standard document (the Ada RM) so that provides an overall organization if the sources follow it closely (which they do for GNAT). Following the C standard closely would not be so helpful, and of course there is no analogous standard for the back end.