From: Robert Zeh <rzeh@efs-us.com>
To: gdb@sources.redhat.com
Subject: Re: gdb, c++ & namespaces
Date: Thu, 15 Jan 2004 14:26:00 -0000 [thread overview]
Message-ID: <4006A2B2.7090401@efs-us.com> (raw)
In-Reply-To: <20040115125112.182744B104@berman.michael-chastain.com>
Michael Elizabeth Chastain wrote:
>eli> The manual doesn't mention "static type" and "dynamic type" in the
>eli> section that describes "set pruint". I think it should, if this
>eli> terminology is to be widely accepted.
>
>I don't know what the popular usage in the C++ community is.
>I don't want to invent new phrases if there are existing phrases.
>
>I checked "The C++ Programming Language" and it does not have
>any nice phrases to distinguish "the type that the pointer says"
>versus "the type that the object in memory has".
>
>Michael C
>
>
>
I believe "static type" and "dynamic type" are the correct phrases to
use. They correspond nicely to C++'s static_cast and dynamic_cast
operators. They also match Stroustrup's discussion in section 24.2.3 of
"The C++ Programming Language" (3rd edition). He refers to the runtime
types as the dynamic type, and type known at compile time as the static
type.
Robert Zeh
next prev parent reply other threads:[~2004-01-15 14:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 12:51 Michael Elizabeth Chastain
2004-01-15 14:07 ` Marcel Lanz
2004-01-15 14:26 ` Robert Zeh [this message]
2004-01-16 22:09 ` Gabriel Dos Reis
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 14:17 Michael Elizabeth Chastain
2004-01-14 14:26 ` Marcel Lanz
2004-01-15 8:02 ` Eli Zaretskii
2004-01-16 22:04 ` Gabriel Dos Reis
2004-01-14 12:02 Michael Elizabeth Chastain
2004-01-14 12:43 ` Marcel Lanz
2004-01-14 13:49 ` Marcel Lanz
2004-01-14 13:55 ` Daniel Jacobowitz
2004-01-14 15:29 ` Andrew Cagney
2004-01-14 15:35 ` Marcel Lanz
2004-01-14 16:00 ` Andrew Cagney
2004-01-14 11:36 Michael Elizabeth Chastain
2004-01-14 11:54 ` Marcel Lanz
2004-01-14 10:16 Marcel Lanz
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=4006A2B2.7090401@efs-us.com \
--to=rzeh@efs-us.com \
--cc=gdb@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