From: Michael Snyder <msnyder@specifix.com>
To: Jim Blandy <jimb@red-bean.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Rob Quill <rob.quill@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: New scope checking patch
Date: Thu, 31 Jan 2008 07:52:00 -0000 [thread overview]
Message-ID: <1201762969.3263.253.camel@localhost.localdomain> (raw)
In-Reply-To: <8f2776cb0801301557t2e265b62u56d6df7cbcec1c84@mail.gmail.com>
On Wed, 2008-01-30 at 15:57 -0800, Jim Blandy wrote:
> On Jan 30, 2008 10:20 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > I actually think that this feature should be described in the node
> > "Convenience Vars", not in "Variables". The latter describes how to
> > refer to variables in the program being debugged; while $in_scope is
> > related (and should perhaps be cross-referenced from "Variables"),
> > that is not the right place for describing GDB built-ins.
>
> That's kind of an interesting point. This is an entirely new kind of
> entity: it's not a convenience variable, it's a convenience function,
> or perhaps a new operator. I'm not sure where it should go. I'd
> expect the primary description to be in "Expressions", in the part
> that says, "GDB supports these operators, in addition to those common
> to programming languages".
Maybe we could have a discussion about what sorts of operators
gdb might provide in this context.
The canonical example for me of a missing functionality is
"offsetof" (in the sense of "sizeof"). I suppose in that
spirit, I might like to have "typeof", and "scopeof".
Maybe for C++ or objective-C, "classof"...
next prev parent reply other threads:[~2008-01-31 7:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 16:29 Rob Quill
2007-11-12 23:26 ` Michael Snyder
2008-01-10 1:00 ` Jim Blandy
2008-01-11 0:52 ` Rob Quill
2008-01-11 22:51 ` Jim Blandy
2008-01-14 23:07 ` Michael Snyder
2008-01-15 17:06 ` Jim Blandy
2008-01-17 19:32 ` Rob Quill
2008-01-17 20:15 ` Jim Blandy
2008-01-17 21:11 ` Rob Quill
2008-01-17 21:58 ` Jim Blandy
2008-01-17 23:40 ` Doug Evans
2008-01-18 1:31 ` Daniel Jacobowitz
2008-01-18 3:35 ` Rob Quill
2008-01-18 18:48 ` Jim Blandy
2008-01-18 22:43 ` Rob Quill
2008-01-19 0:38 ` Jim Blandy
2008-01-30 13:11 ` Rob Quill
2008-01-30 18:14 ` Jim Blandy
2008-01-30 18:31 ` Eli Zaretskii
2008-01-31 4:11 ` Jim Blandy
2008-01-31 7:26 ` Eli Zaretskii
2008-07-27 23:45 ` Rob Quill
2008-07-28 3:18 ` Eli Zaretskii
2008-07-28 10:31 ` Rob Quill
2008-07-28 18:27 ` Eli Zaretskii
2008-07-29 20:31 ` Tom Tromey
2008-07-29 21:04 ` Rob Quill
2008-07-29 21:45 ` Tom Tromey
2008-07-29 22:53 ` Rob Quill
2008-07-30 3:34 ` Tom Tromey
2008-10-23 13:42 ` Convenience functions (was: Re: New scope checking patch) Daniel Jacobowitz
2008-10-23 15:17 ` Convenience functions Tom Tromey
2008-10-23 15:22 ` Daniel Jacobowitz
2008-10-23 15:26 ` Tom Tromey
2008-10-23 19:14 ` Tom Tromey
2008-10-24 12:53 ` Eli Zaretskii
2008-11-04 21:37 ` Convenience functions (was: Re: New scope checking patch) Thiago Jung Bauermann
2008-11-04 22:23 ` Daniel Jacobowitz
2008-11-04 22:43 ` Convenience functions Tom Tromey
2008-01-31 7:52 ` Michael Snyder [this message]
2008-01-19 1:35 ` New scope checking patch Michael Snyder
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=1201762969.3263.253.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.com \
--cc=rob.quill@gmail.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