From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: tromey@redhat.com
Cc: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: Handling of structure dereferencing
Date: Thu, 06 Dec 2001 23:36:00 -0000 [thread overview]
Message-ID: <7458-Fri07Dec2001093544+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <87k7vzap57.fsf@creche.redhat.com> (message from Tom Tromey on 06 Dec 2001 16:45:56 -0700)
> From: Tom Tromey <tromey@redhat.com>
> Date: 06 Dec 2001 16:45:56 -0700
>
> However, I do notice that I only use this in the `b' case.
> I don't recall ever using it when there is more than one level of
> indirection involved.
Yeah, that wiould be quite unnatiral, don't you think? I wonder how
many users even know about this feature. I didn't.
next prev parent reply other threads:[~2001-12-07 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 9:07 Daniel Jacobowitz
2001-12-06 11:48 ` Eli Zaretskii
2001-12-06 12:43 ` Daniel Jacobowitz
2002-01-02 20:25 ` Andrew Cagney
2002-02-05 9:31 ` Daniel Berlin
2002-02-05 10:17 ` Daniel Jacobowitz
2001-12-06 15:41 ` Tom Tromey
2001-12-06 23:36 ` Eli Zaretskii [this message]
2001-12-06 9:46 Michael Elizabeth Chastain
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=7458-Fri07Dec2001093544+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--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