From: "Martin M. Hunt" <hunt@redhat.com>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Differences between new watch window and old
Date: Wed, 06 Nov 2002 14:55:00 -0000 [thread overview]
Message-ID: <1036623380.1106.66.camel@localhost.localdomain> (raw)
I forgot to mention some of the new features/changes.
- Watch window allows variables with the same names.
This made it impossible to use the old watch window when you are
debugging functions that reuse variable names. This is very common.
- Watch window indicates which variables are not currently in scope.
This commonly resulted in misleading results where you saw variable "n"
(for example) in the watch window and it had a completely different
value that the "n" in the current function.
- On the old watch window when you clicked on the "+" and opened up a
struct or pointer, then stepped out of scope, it closed. Then when you
step into scope again, it remains closed. This was VERY annoying.
- New window displays type information.
- Popup menu now includes Sort, Help, and Close
- "Sort" alphabetizes the variables in a window. I wanted drag-n-drop,
but it isn't done yet.
- Faster, smaller, more flexible.
- Does not use Tix, which is good because we are removing Tix soon.
Martin
reply other threads:[~2002-11-06 22:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1036623380.1106.66.camel@localhost.localdomain \
--to=hunt@redhat.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).