public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: law@redhat.com
To: Diego Novillo <dnovillo@redhat.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa] coding style for structure fields
Date: Mon, 03 Mar 2003 17:04:00 -0000	[thread overview]
Message-ID: <200303031602.h23G2x9A002007@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "03 Mar 2003 10:40:13 EST." <1046706013.29022.11.camel@tornado>

In message <1046706013.29022.11.camel@tornado> , Diego Novillo writes:
 >I think I'm getting sick of this.  I see two problems:
Can't blame you.  I'm not a big fan of the inline accessor functions :-)


 >I realize that these stylistic issues are highly subjective, but I'd
 >like to get an idea of what other folks think.  Should we move inline
 >with the rest of GCC and use lvalue-macros?  Should we maintain the
 >current get/set inline macros?
I would recommend you use the schemes used elsewhere in GCC, namely
lvalue macros.

jeff

      reply	other threads:[~2003-03-03 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 16:33 Diego Novillo
2003-03-03 17:04 ` law [this message]

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=200303031602.h23G2x9A002007@speedy.slc.redhat.com \
    --to=law@redhat.com \
    --cc=dnovillo@redhat.com \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).