Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: mec.gnu@mindspring.com (Michael Elizabeth Chastain),
	marcel.lanz@ds9.ch, gdb@sources.redhat.com
Subject: Re: gdb, c++ & namespaces
Date: Fri, 16 Jan 2004 22:04:00 -0000	[thread overview]
Message-ID: <m3n08nzhd4.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <9743-Thu15Jan2004095829+0200-eliz@elta.co.il>

"Eli Zaretskii" <eliz@elta.co.il> writes:

| > Date: Wed, 14 Jan 2004 09:17:30 -0500 (EST)
| > From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
| > 
| >   (gdb) set print object off
| >   (gdb) print *dp
| >   (gdb) set print object on
| >   (gdb) print *dp
| > 
| > When "set print object" is off, gdb will print an object of the type
| > of the pointer (we call this the "static type").  When "set print object"
| > is on, gdb will print the type of the object in memory (we call this
| > the "dynamic type".
| 
| The manual doesn't mention "static type" and "dynamic type" in the
| section that describes "set pruint".  I think it should, if this
| terminology is to be widely accepted.

The phrases "static type" and "dynamic type" are standard terms with
precise meanings used to describe Standard C++.  
"static type" is the type of the expression, as  determined by static
analysis (i.e. at compile-time) to access and object.
"dynamic type" is what the C standard would call the "effective type".
It is the type of the object as determined at its construction/creation.  
See the first chapter of the C++ standard.

-- Gaby


  reply	other threads:[~2004-01-16 22:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-15 12:51 Michael Elizabeth Chastain
2004-01-15 14:07 ` Marcel Lanz
2004-01-15 14:26 ` Robert Zeh
2004-01-16 22:09 ` 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=m3n08nzhd4.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=eliz@elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=marcel.lanz@ds9.ch \
    --cc=mec.gnu@mindspring.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