From: "Eli Zaretskii" <eliz@elta.co.il>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/doco] add obstacks to gdbint.texi
Date: Tue, 10 Feb 2004 20:06:00 -0000 [thread overview]
Message-ID: <7494-Tue10Feb2004220655+0200-eliz@elta.co.il> (raw)
In-Reply-To: <16425.13661.237505.892571@localhost.redhat.com> (message from Elena Zannoni on Tue, 10 Feb 2004 14:47:41 -0500)
> From: Elena Zannoni <ezannoni@redhat.com>
> Date: Tue, 10 Feb 2004 14:47:41 -0500
> >
> > I would put "obstack" either in @code or in @samp.
>
> all over or just that sentence?
All over, I think.
> > Finally, there are many places where there's only one blank after a
> > dot that ends a sentence. Please make that 2 spaces.
>
> Ok, is there something in .emacs that I should set to get this done when
> I do an 'esc-q' for instance?
It does that for me by default. If it doesn't for you, perhaps you
have sentence-end-double-space set to nil somehow.
> +An essential and convenient property of all data on obstacks is that
> +memory for it gets allocated (with obstack_alloc) at various times
> +during a debugging sesssion, but it is released all at once using the
> +obstack_free function. The obstack_free function takes a pointer to
> +where in the stack it must start the deletion from (much like the
> +cleanup chains have a pointer to where to start the cleanups).
obstack_free, obstack_alloc, etc. are functions, so they need @code.
Otherwise, fine; thanks.
next prev parent reply other threads:[~2004-02-10 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 17:31 Elena Zannoni
2004-02-10 19:04 ` Eli Zaretskii
2004-02-10 19:51 ` Elena Zannoni
2004-02-10 20:06 ` Eli Zaretskii [this message]
2004-02-10 20:38 ` Elena Zannoni
2004-02-11 6:09 ` Eli Zaretskii
2004-02-11 15:41 ` Elena Zannoni
2004-02-11 19:27 ` Eli Zaretskii
2004-02-10 19:30 ` Daniel Jacobowitz
2004-02-10 20:06 ` Elena Zannoni
2004-02-10 20:11 ` Daniel Jacobowitz
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=7494-Tue10Feb2004220655+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=ezannoni@redhat.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