Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@dberlin.org>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Neil Booth <neil@daikokuya.demon.co.uk>,
	Jim Blandy <jimb@redhat.com>, <gdb-patches@sources.redhat.com>,
	<gcc@gcc.gnu.org>
Subject: Re: RFC: C/C++ preprocessor macro support for GDB
Date: Mon, 18 Mar 2002 05:32:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0203180813210.21768-100000@dberlin.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0203180751300.21768-100000@dberlin.org>

On Mon, 18 Mar 2002, Daniel Berlin wrote:

> On Mon, 18 Mar 2002, Zack Weinberg wrote:
> 
> > On Mon, Mar 18, 2002 at 03:05:59AM -0500, Daniel Berlin wrote:
> > > I *really* don't see why Jim went to all the trouble, since it would 
> > > probably have taken less than half a week to add the necessary 
> > > changes to libcpp.
> > 
> > This level of opprobrium is not constructive.

And am I the only one who had to look up the work opprobrium?

If you think i've got some amount of "contempt" or "reproach", in this 
case, you would be 
right.
This was a discussion that didn't just take place on the gcc list.
It took place on gdb's as well, last june.

You'll note I had already hooked up cpplib at that point.
You'll also note he wanted cpplib's expansion code decoupled, and I 
explained this was going to happen (since we had the gcc discussion at 
that point), and I was told it wasn't necessary.
In other words, we've been through this before, with the exact same 
people and issues.
And as Stan Shebs pointed out back then, one of the purposes of cpplib was 
to be able to be reused by gdb.
So your right that i've got a bit of contempt when we go through it all 
again, when it could have been avoided by simply communicating.

--Dan


  reply	other threads:[~2002-03-18 13:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-16 22:23 Jim Blandy
2002-03-17  0:11 ` Zack Weinberg
2002-03-17 19:33   ` Jim Blandy
2002-03-17  4:46 ` Neil Booth
2002-03-17 20:35   ` Jim Blandy
2002-03-17 23:29     ` Neil Booth
2002-03-18  0:06       ` Daniel Berlin
2002-03-18  0:36         ` Zack Weinberg
2002-03-18  5:00           ` Daniel Berlin
2002-03-18  5:32             ` Daniel Berlin [this message]
2002-03-18 11:18           ` Jim Blandy
2002-03-18 12:09             ` Neil Booth
2002-03-18 10:45         ` Neil Booth
2002-03-18 11:45           ` Stan Shebs
2002-03-18 12:05             ` Neil Booth
2002-03-18 12:19               ` Stan Shebs
2002-03-18 15:45             ` Jim Blandy
2002-03-18  7:16     ` Andrew Cagney
2002-03-17  9:07 ` Daniel Berlin
2002-03-17 16:53   ` Daniel Berlin
2002-03-18  7:35 ` Batons? Was: " Andrew Cagney
2002-03-18 12:08   ` Jim Blandy
2002-03-18 12:55     ` Andrew Cagney
2002-03-18 15:49       ` Jim Blandy
2002-03-18  7:39 ` Andrew Cagney
2002-03-19 13:16   ` Jim Blandy
2002-03-18 10:34 ` Neil Booth
2002-03-18 11:11   ` Neil Booth
2002-03-18 16:03   ` Jim Blandy
2002-03-18 17:42     ` Stan Shebs
2002-03-18 19:51   ` Jim Blandy
2002-03-18 23:23     ` Neil Booth
2002-03-18 20:33   ` Jim Blandy
2002-03-23 12:14 ` Andrew Cagney

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=Pine.LNX.4.44.0203180813210.21768-100000@dberlin.org \
    --to=dan@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=neil@daikokuya.demon.co.uk \
    --cc=zack@codesourcery.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