qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, av1474@comtv.ru
Cc: paul@codesourcery.com
Subject: Re: [Qemu-devel] [RFC] Introduce module API to QEMU
Date: Fri, 03 Apr 2009 11:59:52 -0600 (MDT)	[thread overview]
Message-ID: <20090403.115952.-1581798123.imp@bsdimp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0904032139110.2406@linmac.oyster.ru>

In message: <Pine.LNX.4.64.0904032139110.2406@linmac.oyster.ru>
            malc <av1474@comtv.ru> writes:
: On Fri, 3 Apr 2009, Anthony Liguori wrote:
: 
: > malc wrote:
: > > You are using _identifier_ whose name violates 7.1.3, full stop, you
: > > can not do that in _any_ context.
: > >   
: > 
: > So then we cannot use __func__ either or __attribute__ by your logic.
: 
: a) __func__ is 6.4.2.2#1
: 
: b) __attribute__ is exactly the implementation defined keyword that
:    6.5.2 31) i referenced earlier describes, so no you can not use
:    that in a portable code and yes you can use it in code that is
:    GCC specific and properly guarded

To back this discussion off a notch on the grumpiness scale...

The objection here is that you don't HAVE to use identifiers starting
with __, and using them is dangerous, so why not just remove the __
from the start and get on with your life?

Warner

  reply	other threads:[~2009-04-03 18:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03  2:12 [Qemu-devel] [RFC] Introduce module API to QEMU Anthony Liguori
2009-04-03  2:29 ` malc
2009-04-03  3:36   ` Anthony Liguori
2009-04-03  3:48     ` malc
2009-04-03 12:59       ` Anthony Liguori
2009-04-03 17:00         ` malc
2009-04-03 17:31           ` Anthony Liguori
2009-04-03 17:46             ` malc
2009-04-03 17:59               ` M. Warner Losh [this message]
2009-04-03 17:58             ` M. Warner Losh
2009-04-03 18:05               ` Anthony Liguori
2009-04-03 20:12               ` Kevin Wolf
2009-04-03 18:30                 ` malc
2009-04-03  7:08 ` Mark McLoughlin
2009-04-03 13:01   ` Anthony Liguori
2009-04-03 17:36   ` Anthony Liguori
2009-04-03  7:50 ` Avi Kivity
2009-04-03 11:35 ` Paul Brook
2009-04-03 12:57   ` Anthony Liguori
2009-04-03 13:09     ` Paul Brook
2009-04-03 14:10       ` Anthony Liguori
2009-04-03 14:11       ` Anthony Liguori
2009-04-03 14:28         ` Paul Brook
2009-04-03 14:53         ` Avi Kivity
2009-04-03 16:15           ` Anthony Liguori
2009-04-03 17:12     ` Blue Swirl
2009-04-03 14:04 ` Daniel Jacobowitz
2009-04-03 14:54   ` Avi Kivity
2009-04-03 15:10     ` Paul Brook

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=20090403.115952.-1581798123.imp@bsdimp.com \
    --to=imp@bsdimp.com \
    --cc=av1474@comtv.ru \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).