Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eager@eagercon.com
Cc: brobecker@adacore.com, gdb@sourceware.org
Subject: Re: GDB in C++
Date: Tue, 03 Jul 2007 07:55:00 -0000	[thread overview]
Message-ID: <200707030755.l637tP9e011986@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <1183434310.4689c646a3bd2@myaccount.bayarea.net> (message from 	Michael Eager on Mon, 2 Jul 2007 20:45:10 -0700)

> Date: Mon,  2 Jul 2007 20:45:10 -0700
> From: Michael Eager <eager@eagercon.com>
> 
> Quoting Joel Brobecker <brobecker@adacore.com>:
> 
> > > I'm in favor of switching to C++.  I'm not going to argue about it if
> > > others disagree, but I'll offer to do most of the work if the
> > > consensus is positive.
> >
> > I am against this change. I'm not going to argue either, because there
> > are some technical merits on both sides, and they have been discussed
> > to death.
> >
> > However, I think that requiring a C++ compiler will make it harder
> > for some users to build GDB, just because C++ compilers are not
> > always as readily available as C compilers.
> 
> What currently supported hosts do not have a C++ compiler?

If you consider GCC 2.95.3 a proper C++ compiler, probably none.  And
don't expect exception handling to work reliable.

> I think that this may have been a valid concern several years
> ago, but I think the lack of C++ compilers is no longer the case.

The lack of a standards compliant C++ compiler still is though.  You
can probably find a subset of the language that will work on all major
C++ compilers, but how are you going to enforce people to restrict
themselves to that subset?

Then there is the problem that with C++ compilers are generally slower
and need more memory than C compilers.  This is certainly true for
GCC.  We can currently build GDB on OpenBSD/mac68k and OpenBSD/vax on
machines with less than 32 MB of memory.  

Anyway, end of discussion as far as I'm concerned.


  reply	other threads:[~2007-07-03  7:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30 14:56 Michael Eager
2007-07-01 20:54 ` Daniel Jacobowitz
2007-07-02  1:33   ` Joel Brobecker
2007-07-03  3:49     ` Michael Eager
2007-07-03  7:55       ` Mark Kettenis [this message]
2007-07-11 21:04     ` Jan Kratochvil
2007-07-02  7:21   ` Mark Kettenis
2007-07-03  3:57     ` Michael Eager
2007-07-03  7:03       ` Fabian Cenedese
2007-07-03 12:14         ` Robert Dewar
2007-07-03 19:09           ` Gary Funck
2007-07-11 19:47             ` Thiago Jung Bauermann
2007-07-11 19:59               ` Paul Koning
2007-07-11 20:41                 ` Jim Blandy
2007-07-11 21:00                   ` Gary Funck
2007-07-11 21:32                   ` Daniel Jacobowitz
2007-07-11 21:38                     ` Robert Dewar
2007-07-12  3:16                     ` Eli Zaretskii
2007-07-12  2:24               ` Michael Eager
2007-07-13 20:21                 ` Thiago Jung Bauermann
2007-07-13 20:55                   ` Eli Zaretskii
2007-07-13 21:24                     ` Thiago Jung Bauermann
2007-07-12  3:11               ` Eli Zaretskii
2007-07-11 21:11           ` Gary Funck
2007-07-02 20:21   ` David Daney
2007-07-02 20:28     ` Daniel Jacobowitz

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=200707030755.l637tP9e011986@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=eager@eagercon.com \
    --cc=gdb@sourceware.org \
    /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