Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eliz@gnu.org
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [commit] Convert COERCE_* to functions
Date: Thu, 11 Nov 2004 20:14:00 -0000	[thread overview]
Message-ID: <200411112014.iABKE2qS098672@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <01c4c826$Blat.v2.2.2$10ab7100@zahav.net.il> (eliz@gnu.org)

   Date: Thu, 11 Nov 2004 21:37:45 +0200
   From: "Eli Zaretskii" <eliz@gnu.org>

   > Date: Thu, 11 Nov 2004 11:36:57 -0500
   > From: Andrew Cagney <cagney@gnu.org>
   > Cc: gdb-patches@sources.redhat.com
   > 
   > > 1) Can you tell the reason for these changes?
   > > 
   > > 2) Personally, I think that
   > > 
   > >      foo = foobar (foo);
   > > 
   > >    is not a good style of C programming.
   > 
   > opaque `struct value'
   > http://sources.redhat.com/ml/gdb/2004-11/msg00010.html

   Thanks.  Perhaps it would help in the future to post the URL with the
   patch.

Come on Eli.  This patch came a few days after Andrew announced he was
going to make `struct value' opaque.

   > Converting a macro to a function has for a long time been considered 
   > obvious.

   I don't think it's obvious, but if I'm the only one, let's codify that
   where we say what falls under the ``obvious'' rule.

Codifying this kind of details is stupid.  Codifying the general rules
should be enough.

Mark


  reply	other threads:[~2004-11-11 20:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 19:03 Andrew Cagney
2004-11-10 20:04 ` Eli Zaretskii
2004-11-11 16:38   ` Andrew Cagney
2004-11-11 19:44     ` Eli Zaretskii
2004-11-11 20:14       ` Mark Kettenis [this message]
2004-11-12 13:08         ` Eli Zaretskii

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=200411112014.iABKE2qS098672@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=cagney@gnu.org \
    --cc=eliz@gnu.org \
    --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