From: Stan Shebs <stanshebs@earthlink.net>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Special casing dtors?
Date: Thu, 26 Mar 2009 22:39:00 -0000 [thread overview]
Message-ID: <49CC005E.3010500@earthlink.net> (raw)
In-Reply-To: <49CAB139.8010100@redhat.com>
Keith Seitz wrote:
> Hi,
>
> I've been looking a bit at a patch (in Fedora) which fixes prms/1112,
> and I notice that both valops.c and linespec.c treat destructors as
> "special case"s -- but nowhere does it say WHY.
>
> I've searched through all the history I can find about this (including
> the Cygnus internal ueberbaum), and all I've been able to discover is
> that this has been in a LONG time (before 1990).
1980s C++ was rather a different language from today, and G++ was even
more different, so it could easily have been something that made sense
for 1.x and not anything later.
Stan
next prev parent reply other threads:[~2009-03-26 22:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 22:39 Keith Seitz
2009-03-26 22:07 ` Tom Tromey
2009-03-26 22:39 ` Stan Shebs [this message]
2009-03-27 2:35 ` Daniel Jacobowitz
2009-03-27 8:07 ` Keith Seitz
2009-03-27 15:06 ` Pedro Alves
2009-03-27 15:41 ` Joel Brobecker
2009-03-27 17:19 ` Keith Seitz
2009-03-27 17:49 ` Pedro Alves
2009-03-27 19:05 ` Keith Seitz
2009-03-27 19:22 ` Pedro Alves
2009-03-28 0:56 ` Keith Seitz
2009-03-28 8:56 ` Keith Seitz
2009-03-30 21:46 ` Pedro Alves
2009-04-01 23:48 ` Keith Seitz
2009-04-02 3:17 ` Daniel Jacobowitz
2009-04-02 16:25 ` Keith Seitz
2009-04-02 16:32 ` Daniel Jacobowitz
2009-04-02 8:27 ` Mark Kettenis
2009-04-07 20:54 ` Pedro Alves
2009-04-07 21:26 ` Keith Seitz
2009-04-24 6:06 ` Tom Tromey
2009-04-24 17:54 ` Keith Seitz
2009-04-24 22:49 ` Tom Tromey
2009-06-16 18:41 ` Keith Seitz
2009-03-28 21:19 ` Tom Tromey
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=49CC005E.3010500@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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