Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: tromey@redhat.com, aoliva@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFC][Python] Re: any expression to tell whether a variable was	optimized out?
Date: Mon, 23 Mar 2009 04:24:00 -0000	[thread overview]
Message-ID: <uljqwooil.fsf@gnu.org> (raw)
In-Reply-To: <1237771863.25721.17.camel@localhost.localdomain>

> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> Cc: Alexandre Oliva <aoliva@redhat.com>, gdb-patches@sourceware.org
> Date: Sun, 22 Mar 2009 22:31:02 -0300
> 
> +@table @code
> +@defmethod Value is_optimized_out
> +This read-only boolean attribute is true if the compiler optimized out
> +this value, thus it is not available for fetching from the inferior.
> +@end defmethod
> +@end table

This is OK, but please add a @cindex entry for this that starts with
"optimized", so that readers will be able to find this easier.

Thanks.


  reply	other threads:[~2009-03-23  4:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <orskllhfo3.fsf@oliva.athome.lsd.ic.unicamp.br>
     [not found] ` <20090310125945.GA4376@caradoc.them.org>
     [not found]   ` <1236700079.11106.1.camel@localhost.localdomain>
     [not found]     ` <orzlftfhu1.fsf@oliva.athome.lsd.ic.unicamp.br>
     [not found]       ` <1236710732.11106.30.camel@localhost.localdomain>
     [not found]         ` <m3hc1rluz1.fsf@fleche.redhat.com>
2009-03-23  2:09           ` Thiago Jung Bauermann
2009-03-23  4:24             ` Eli Zaretskii [this message]
2009-03-26 21:21               ` Thiago Jung Bauermann
2009-03-23 17:47             ` Tom Tromey
2009-03-28 21:38               ` [RFA][Python] Change gdb.Value.address from a method to an attribute Thiago Jung Bauermann
2009-03-29  4:21                 ` Eli Zaretskii
2009-03-29 18:12                   ` Tom Tromey
2009-03-29 18:56                     ` Eli Zaretskii
2009-03-29 21:22                       ` Thiago Jung Bauermann
2009-03-29 15:42                 ` Tom Tromey

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=uljqwooil.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aoliva@redhat.com \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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