From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] some mindless additions of BLOCK_ macros
Date: Wed, 23 Oct 2002 16:50:00 -0000 [thread overview]
Message-ID: <ro14rbc3ebv.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20021023232424.GA4331@nevyn.them.org>
On Wed, 23 Oct 2002 19:24:24 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> I admit C++ grows more attractive every passing day though. Thing
> we can take the leap, in a few years maybe?
Maybe I'll just start doing 'make CC=g++' on
carlton_dictionary-branch... (It already has code in it with
hand-rolled vtables.) Alas, that wouldn't work, but I'll just start
submitting little patches that, say, rename every variable in GDB
called 'namespace' to something else, to avoid gratuitous conflicts.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-10-23 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 14:17 David Carlton
2002-10-23 16:04 ` Andrew Cagney
2002-10-23 16:19 ` David Carlton
2002-10-23 16:59 ` Andrew Cagney
2002-10-23 17:20 ` David Carlton
2002-10-23 16:24 ` Daniel Jacobowitz
2002-10-23 16:50 ` David Carlton [this message]
2002-10-23 17:18 ` Elena Zannoni
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=ro14rbc3ebv.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@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