Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] New command: ``start''
Date: Tue, 18 May 2004 18:42:00 -0000	[thread overview]
Message-ID: <9743-Tue18May2004210526+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040518170517.GF31800@gnat.com>

> Date: Tue, 18 May 2004 10:05:17 -0700
> From: Joel Brobecker <brobecker@gnat.com>
> 
> Just one additional comment, that may not be obvious: In Ada, the name
> of the main procedure is not specified by Ada, it's up to the user to
> choose it. That means that the name of that main procedure depends on
> the program. When Ada-support is activated, we'll implement our own
> main_procedure_name method that will dig out that name from the
> executable. JIC.

Understood.

> > Please use "C@t{++}" instead of "C++", the former looks prettier in
> > print.
> 
> Fixed.

Thanks, but there's still one place where "C++" is used ;-)

> I tried to make it more explanatory by explaining what happens during
> the elaboration (some code is run before the main procedure is called),
> and also by providing an example using C++ constructors.

Okay, this is much more clear now.  Perhaps it would be useful to
mention the term ``startup code'' there?

> > You mean, if you type "run" thereafter, it will reuse the arguments
> > you type for the "start" command?  If so, we should reword this text
> > to make that more clear.  ``Directly passed'' is confusing, since
> > nothing is really passed anywhere.
> 
> I have reworked the documentation. Is it better?

It's much better, thanks.  However, I understand that the same
arguments will be reused later if the user invokes "run", is that
true?  If so, I think we should mention that.

> +@table @code
> +@kindex start

I think an additional index entry here saying

  @cindex run to main procedure

would help.

Otherwise, the documentation patch is approved; thanks.

For the code patch, please wait for the responsible person(s) to give
their final blessing.  (Hmm... who is that in this case? MAINTAINERS
says "Blanket Write Privs Maintainers".  Andrew?)


  reply	other threads:[~2004-05-18 18:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18  2:47 Joel Brobecker
2004-05-18  6:32 ` Eli Zaretskii
2004-05-18 17:05   ` Joel Brobecker
2004-05-18 18:42     ` Eli Zaretskii [this message]
2004-05-18 19:03       ` Andrew Cagney
2004-05-19  5:39         ` Eli Zaretskii
2004-05-18 19:22       ` Joel Brobecker
2004-05-18 21:47 ` Daniel Jacobowitz
2004-05-18 22:27   ` Joel Brobecker
2004-05-18 22:41     ` Daniel Jacobowitz
2004-05-19 15:36       ` Joel Brobecker
2004-05-19 15:42         ` Daniel Jacobowitz
2004-05-19 16:10           ` Joel Brobecker
2004-05-20  1:01           ` Joel Brobecker
2004-05-20  5:29             ` Eli Zaretskii
2004-05-20 13:46             ` Daniel Jacobowitz
2004-05-20 16:03               ` Joel Brobecker
2004-05-20 17:14                 ` Daniel Jacobowitz
2004-05-20 20:33                   ` Paul Gilliam
2004-05-20 22:12                   ` Joel Brobecker
2004-05-21  0:26                     ` Daniel Jacobowitz
2004-05-21  1:31                       ` Joel Brobecker
2004-05-24 22:24                         ` Daniel Jacobowitz
2004-05-24 23:57                           ` Joel Brobecker
2004-05-19 14:30 ` Andrew Cagney
2004-05-19 15:39   ` Joel Brobecker
2004-05-19 20:02     ` Eli Zaretskii
2004-05-21 18:57       ` Andrew Cagney
2004-05-18 19:30 Michael Elizabeth Chastain
2004-05-18 19:45 ` Joel Brobecker
2004-05-18 20:21 Michael Elizabeth Chastain

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=9743-Tue18May2004210526+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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