From: Tom Tromey <tromey@redhat.com>
To: Insight List <insight@sourceware.cygnus.com>
Subject: balloon -vs- enums
Date: Tue, 16 Oct 2001 11:31:00 -0000 [thread overview]
Message-ID: <87ofkqde7p.fsf@creche.redhat.com> (raw)
This is a line from gcj:
2659 && reloc->kind == OPCODE_goto_w
Here, `reloc->kind' is an `int', and OPCODE_goto_w is defined in an
enum. If I hold the mouse over the latter, the balloon comes up and
says:
OPCODE_goto_w=OPCODE_goto_w
It would be nice if instead insight showed:
OPCODE_goto_w=(enum java_opcode) 200
Or something similar.
Tom
WARNING: multiple messages have this Message-ID
From: Tom Tromey <tromey@redhat.com>
To: Insight List <insight@sourceware.cygnus.com>
Subject: balloon -vs- enums
Date: Sat, 22 Dec 2001 15:22:00 -0000 [thread overview]
Message-ID: <87ofkqde7p.fsf@creche.redhat.com> (raw)
Message-ID: <20011222152200.iEr7ZfuQSBtttOxv3FnYlrEKC4apGGN4xFuxo9wqz7A@z> (raw)
This is a line from gcj:
2659 && reloc->kind == OPCODE_goto_w
Here, `reloc->kind' is an `int', and OPCODE_goto_w is defined in an
enum. If I hold the mouse over the latter, the balloon comes up and
says:
OPCODE_goto_w=OPCODE_goto_w
It would be nice if instead insight showed:
OPCODE_goto_w=(enum java_opcode) 200
Or something similar.
Tom
next reply other threads:[~2001-12-22 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 11:31 Tom Tromey [this message]
2001-12-22 15:22 ` 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=87ofkqde7p.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).