From: Trevor Saunders <tsaunders@mozilla.com>
To: gcc@gcc.gnu.org
Subject: Re: replace do-while macros with static inline functions
Date: Fri, 13 Dec 2013 19:42:00 -0000 [thread overview]
Message-ID: <20131213194223.GB31212@tsaunders-iceball.corp.tor1.mozilla.com> (raw)
In-Reply-To: <CAJXstsBweJk9TkDp8S3DYm_MKeMJ2AErta36fcxevJnTH0JqVQ@mail.gmail.com>
On Wed, Dec 11, 2013 at 08:33:03PM +0530, Prathamesh Kulkarni wrote:
> I was wondering if it was a good idea to replace do-while macros with
> static inline functions returning void, where appropriate ?
> By "where appropriate" I mean:
> a) call to macro contains no side-effects
> b) macro does not modify the arguments.
> c) macro does not use any preprocessor operators (like ##)
> d) macro does not get undefined or is conditionally defined.
> e) macro is not type independent (use inline template for these?)
> f) Any other case ?
in general I'm infavor of replacing macros with unctions / constants /
templates etc.
> Example:
> Consider C_EXPR_APPEND macro defined in c-tree.h:
>
> /* Append a new c_expr_t element to V. */
> #define C_EXPR_APPEND(V, ELEM) \
> do { \
> c_expr_t __elem = (ELEM); \
> vec_safe_push (V, __elem); \
> } while (0)
Its not my code, but that macro looks like a totally useless
abstruction, why not just inline the vec_safe_push() ?
Trev
>
> It is called at two places in c-parser.c:
> 0 c-parser.c <global> 6140 C_EXPR_APPEND (cexpr_list, expr);
> 1 c-parser.c <global> 6145 C_EXPR_APPEND (cexpr_list, expr);
>
> Shall be replaced by:
>
> static inline void
> C_EXPR_APPEND( vec<c_expr_t, va_gc> * V, c_expr_t ELEM)
> {
> vec_safe_push(V, ELEM);
> }
>
> I will volunteer to do it, if it's accepted.
>
> Thanks and Regards,
> Prathamesh
next prev parent reply other threads:[~2013-12-13 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 15:03 Prathamesh Kulkarni
2013-12-13 19:42 ` Trevor Saunders [this message]
2013-12-13 20:47 ` Ondřej Bílka
[not found] ` <CAD_=9DRy95wpMmLAhrMr8EQ55qcWDzGouhHMckSR2SJMYRemDQ@mail.gmail.com>
2013-12-13 19:48 ` Diego Novillo
2013-12-13 22:06 ` Prathamesh Kulkarni
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=20131213194223.GB31212@tsaunders-iceball.corp.tor1.mozilla.com \
--to=tsaunders@mozilla.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).