Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [doc] improve MI varobj introduction
Date: Tue, 09 Jan 2007 04:18:00 -0000	[thread overview]
Message-ID: <ubql8j0ib.fsf@gnu.org> (raw)
In-Reply-To: <E1H40o1-00012M-A3@zigzag.lvk.cs.msu.su> (message from Vladimir 	Prus on Mon, 08 Jan 2007 23:08:33 +0300)

> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Mon, 08 Jan 2007 23:08:33 +0300
> 
> Again, "that have built-in types" sounds to me like restrictive clause,
> as if there are leaf variables that don't have builtin-types. What about:
> 
>         Recursion ends when we reach leaf variable objects, which always have
>         built-in types.

Fine with me.  (I don't really see the difference between this
sentence and what I wrote.)

> I attach the revised patch, incorporating those two corrections,
> and using the above last sentence. Is it OK, or would you prefer 
> your original sentence? 

It's okay, thanks.


      reply	other threads:[~2007-01-09  4:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19  8:04 Vladimir Prus
2006-12-19 22:29 ` Nick Roberts
2006-12-20 11:47   ` Vladimir Prus
2006-12-20 20:52     ` Nick Roberts
2006-12-21  6:15       ` Vladimir Prus
2006-12-26 15:32         ` Daniel Jacobowitz
2006-12-26 15:52           ` Vladimir Prus
2006-12-26 22:38             ` Daniel Jacobowitz
2007-01-04 18:21               ` Vladimir Prus
2007-01-04 18:23               ` Vladimir Prus
2007-01-04 21:48                 ` Eli Zaretskii
2007-01-05  8:39                   ` Vladimir Prus
2007-01-05  9:26                     ` Eli Zaretskii
2007-01-08 14:50                       ` Vladimir Prus
2007-01-08 19:45                         ` Eli Zaretskii
2007-01-08 20:09                           ` Vladimir Prus
2007-01-09  4:18                             ` Eli Zaretskii [this message]

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=ubql8j0ib.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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