All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] trace: Allow events without arguments
Date: Tue, 13 Sep 2016 16:40:42 +0100	[thread overview]
Message-ID: <20160913154042.GB5677@stefanha-x1.localdomain> (raw)
In-Reply-To: <87k2eppg7u.fsf@fimbulvetr.bsc.es>

[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]

On Tue, Sep 06, 2016 at 10:47:33AM +0200, Lluís Vilanova wrote:
> Stefan Hajnoczi writes:
> 
> > On Fri, Aug 26, 2016 at 11:12:47AM +0200, Lluís Vilanova wrote:
> >> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> >> ---
> >> scripts/tracetool/__init__.py |    5 +++++
> >> 1 file changed, 5 insertions(+)
> >> 
> >> diff --git a/scripts/tracetool/__init__.py b/scripts/tracetool/__init__.py
> >> index be24039..96657e6 100644
> >> --- a/scripts/tracetool/__init__.py
> >> +++ b/scripts/tracetool/__init__.py
> >> @@ -72,6 +72,11 @@ class Arguments:
> >> arg_str : str
> >> String describing the event arguments.
> >> """
> >> +        # check for empty argument list
> >> +        arg_str = arg_str.strip()
> >> +        if arg_str == "":
> >> +            return Arguments([])
> >> +
> 
> > Why is this necessary?  C syntax uses f(void) and not f().
> 
> > We already have trace events with no argument.  They use the correct C
> > syntax.
> 
> Sorry, I wasn't aware of that. My bad.

BTW the details of this syntax difference exists between C and C++:

In C++ foo() means foo(void).

In C you can say foo() but it means something different.  It means the
parameters are unspecified.  You can pass any arguments and the compiler
will do no type-checking!

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

      reply	other threads:[~2016-09-13 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26  9:12 [Qemu-devel] [PATCH] trace: Allow events without arguments Lluís Vilanova
2016-09-05 17:49 ` Stefan Hajnoczi
2016-09-06  8:47   ` Lluís Vilanova
2016-09-13 15:40     ` Stefan Hajnoczi [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=20160913154042.GB5677@stefanha-x1.localdomain \
    --to=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.