From: Robert Dewar <dewar@adacore.com>
To: Robert Dewar <dewar@adacore.com>
Cc: Michael Eager <eager@eagercon.com>,
Paul Koning <pkoning@equallogic.com>,
jimb@codesourcery.com, stanshebs@earthlink.net,
gdb@sources.redhat.com
Subject: Re: What's an annex? stratum?
Date: Mon, 25 Jun 2007 20:47:00 -0000 [thread overview]
Message-ID: <468029CC.6080002@adacore.com> (raw)
In-Reply-To: <4680284E.5010406@adacore.com>
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.
next prev parent reply other threads:[~2007-06-25 20:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 18:01 Michael Eager
2007-06-23 18:57 ` Stan Shebs
2007-06-23 19:08 ` Michael Eager
2007-06-23 19:47 ` Eli Zaretskii
2007-06-23 20:51 ` Michael Eager
2007-06-23 21:23 ` Daniel Jacobowitz
2007-06-23 21:40 ` Michael Eager
2007-06-24 2:58 ` Eli Zaretskii
2007-06-24 4:32 ` Michael Eager
2007-06-25 18:03 ` Jim Blandy
2007-06-25 18:39 ` Michael Eager
2007-06-25 19:10 ` Jim Blandy
2007-06-25 19:26 ` Paul Koning
2007-06-25 19:32 ` Daniel Jacobowitz
2007-06-25 19:38 ` Robert Dewar
2007-06-25 19:48 ` Paul Koning
2007-06-25 20:09 ` Michael Eager
2007-06-25 20:40 ` Robert Dewar
2007-06-25 20:47 ` Robert Dewar [this message]
2007-06-25 20:31 ` Eli Zaretskii
2007-06-25 20:44 ` Robert Dewar
2007-06-25 21:00 ` Eli Zaretskii
2007-06-25 21:03 ` Robert Dewar
2007-06-25 21:06 ` Robert Dewar
2007-06-26 18:34 ` Markus Deuling
2007-06-26 18:36 ` Robert Dewar
2007-06-26 21:55 ` Jim Blandy
2007-06-26 22:14 ` Nick Roberts
2007-06-26 23:26 ` Robert Dewar
2007-06-26 23:39 ` Joel Brobecker
2007-06-26 23:43 ` Robert Dewar
2007-06-27 0:32 ` Jim Blandy
2007-06-27 0:42 ` Robert Dewar
2007-06-27 3:22 ` Eli Zaretskii
2007-06-27 0:23 ` Michael Eager
2007-06-25 20:42 ` Eli Zaretskii
2007-06-25 20:23 ` Eli Zaretskii
2007-06-25 21:52 ` Jim Blandy
2007-06-26 1:04 ` Paul Koning
2007-06-25 20:37 ` Eli Zaretskii
2007-06-25 20:15 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=468029CC.6080002@adacore.com \
--to=dewar@adacore.com \
--cc=eager@eagercon.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@codesourcery.com \
--cc=pkoning@equallogic.com \
--cc=stanshebs@earthlink.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox