From: Daniel Berlin <dberlin@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: zackw@Stanford.EDU, gdb-patches@sources.redhat.com
Subject: Re: Option to elide single-bit bitfields when printing structures
Date: Tue, 27 Feb 2001 11:44:00 -0000 [thread overview]
Message-ID: <m21ysjhpwy.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <200102271904.OAA05522@indy.delorie.com>
Eli Zaretskii <eliz@delorie.com> writes:
> > Date: Tue, 27 Feb 2001 00:16:52 -0800
> > From: "Zack Weinberg" <zackw@Stanford.EDU>
> > >
> > > > > Then IMHO this feature is less helpful than it could be. See the list
> > > > > above: can you really remember all of the flags if they are not shown?
> > > > > And if half of them are shown, is it really easy to know which are and
> > > > > which aren't?
> > > >
> > > > Perhaps you are not familiar with the way these flags get used in gcc.
> > >
> > > I thought you were proposing a general-purpose feature, not something
> > > specific to GCC.
> >
> > I am proposing a general-purpose feature. The GCC usage is a specific
> > example of why it would be useful.
>
> The question is whether there are other examples of why such a limited
> functionality, whereby only single-bit fields which are set can be
> easily displated, would be useful. My experience with debugging
> several large applications (which doesn't include debugging GCC) seems
> to say NO. But that's just me.
I see this type of thing all over the applications i look at, which
consists mainly of compilers and operating systems.
--Dan
next prev parent reply other threads:[~2001-02-27 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010222115633.B11707@wolery.stanford.edu>
[not found] ` <200102230756.CAA06304@indy.delorie.com>
2001-02-23 7:03 ` Daniel Berlin
[not found] ` <6137-Fri23Feb2001183455+0200-eliz@is.elta.co.il>
2001-02-24 13:10 ` Zack Weinberg
2001-02-24 23:53 ` Eli Zaretskii
2001-02-27 0:17 ` Zack Weinberg
2001-02-27 11:04 ` Eli Zaretskii
2001-02-27 11:44 ` Daniel Berlin [this message]
2001-02-27 14:41 ` Michael Snyder
2001-02-23 10:09 ` Michael Snyder
2001-02-24 13:05 ` Zack Weinberg
2001-02-24 23:54 ` Eli Zaretskii
2001-02-27 0:13 ` Zack Weinberg
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=m21ysjhpwy.fsf@dynamic-addr-83-177.resnet.rochester.edu \
--to=dberlin@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=zackw@Stanford.EDU \
/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