Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] [1/5] Types reference counting [base]
Date: Sat, 11 Apr 2009 11:25:00 -0000	[thread overview]
Message-ID: <838wm7301j.fsf@gnu.org> (raw)
In-Reply-To: <20090411102044.GB32624@host0.dyn.jankratochvil.net>

> Date: Sat, 11 Apr 2009 12:20:45 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> 
> a base implementation of types reference counting.

Thanks.

> gdb/doc/

Thanks, I have a few comments about this part of your patch.

> 2009-04-11  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
> 	* gdbint.texinfo (Symbol Handling): New anchor `Builtin Types'.  Move
> 	types `from Memory Management for Symbol Files' to a new subsection
> 	`Memory Management for Types'.

Please also add in the log an entry which explicitly says that `Memory
Management for Types' was added ("New node.").  See below.

> +@subsection Memory Management for Types

I'd prefer not to have sections without an associated @node.  Such a
manual is harder to navigate.  Please add a @node here.  That's
assuming that having a separate subsection here is justified; maybe it
isn't.

Also, a @cindex entry (with the same text as the subsection name, only
in lower case) would be useful here.

> +@code{TYPE_OBJFILE} macro indicates the current memory owner of the type.

It would be good to have a @findex entry for each macro you describe
(TYPE_OBJFILE etc.).

> +@code{TYPE_OBJFILE} set to @code{NULL} and become so called reclaimable types.

"so-called", with a dash, and I suggest a @dfn around "reclaimable
types", since you are introducing new terminology.

> +Types with @code{NULL TYPE_OBJFILE} can be either permanent types

Please don't put @code around several separate words, because that
causes the whitespace to be typeset incorrectly.  Please use a
separate @code for each word.

Actually, I'd reword this as

    Types with @code{TYPE_OBJFILE} set to @code{NULL} can be ..
or
    Types with null @code{TYPE_OBJFILE} can be ...

> +(@pxref{Builtin Types}) or reclaimable types which will be deallocated after the
> +last object referencing them is removed.

But the text below says that actually they will be deallocated only
when GDB becomes idle, right?

> +as through @code{TYPE_TARGET_TYPE}, @code{TYPE_POINTER_TYPE} etc. and prevents
                                                                   ^^
Please add either a @: or a comma after any period that doesn't end a
sentence, so that TeX would not typeset that as a sentence end.


  reply	other threads:[~2009-04-11 11:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 10:21 Jan Kratochvil
2009-04-11 11:25 ` Eli Zaretskii [this message]
2009-04-11 18:15   ` Jan Kratochvil
2009-04-11 19:30     ` Eli Zaretskii
2009-04-11 19:45       ` Jan Kratochvil
2009-04-11 21:10         ` Eli Zaretskii
2009-04-11 21:21           ` Jan Kratochvil
2009-04-16 21:26 ` Tom Tromey
2009-05-25  8:10 ` obsolete: " Jan Kratochvil

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=838wm7301j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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