Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: eliz@elta.co.il, gdb@sources.redhat.com
Subject: Re: gdb, c++ & namespaces
Date: Fri, 16 Jan 2004 22:09:00 -0000	[thread overview]
Message-ID: <m3hdyvzh3s.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <20040115125112.182744B104@berman.michael-chastain.com>

mec.gnu@mindspring.com (Michael Elizabeth Chastain) writes:

| 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.

"static type" and "dynamic type" are not new 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".

I think GDB maintainers should also consult the C++ standard when they
implement support tools for C+ ;-).

   1.3.3 dynamic type
   the type of the most derived object (1.8) to which the lvalue
   denoted by an lvalue expression refers. [Example: if a pointer
   (8.3.1) p whose static type is "pointer to class B" is pointing to
   an object of class D, derived from B (clause 10), the dynamic type
   of the expression *p is "D".  References (8.3.2) are treated
   similarly. ]  The dynamic type of an rvalue is its static type.


   1.3.11 static type
   the type of an expression (3.9), which type results from analysis
   of the program without considering execution semantics. The static
   type of an expression depends only on the form of the program in
   which the expression appears, and does not change while the program
   is executing.  

-- Gaby


  parent reply	other threads:[~2004-01-16 22:09 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
2004-01-16 22:09 ` Gabriel Dos Reis [this message]
  -- 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=m3hdyvzh3s.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=eliz@elta.co.il \
    --cc=gdb@sources.redhat.com \
    --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