LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dave Hylands <dhylands@gmail.com>
To: Sri Ram Vemulpali <sri.ram.gmu06@gmail.com>
Cc: Kernel-newbies <kernelnewbies@nl.linux.org>,
	linux-kernel-mail <linux-kernel@vger.kernel.org>
Subject: Re: typecheck code
Date: Mon, 31 Jan 2011 12:26:15 -0800	[thread overview]
Message-ID: <AANLkTimgTCdJfyKcyrpM-VgWtNCFonu2rvca+pkc+ebh@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimjz6t9ziPajW1wJdUE8ytWy=FbCr-Zg71PiBgf@mail.gmail.com>

Hi Sri,

On Mon, Jan 31, 2011 at 9:03 AM, Sri Ram Vemulpali
<sri.ram.gmu06@gmail.com> wrote:
> Hi all,
>
> /*
>  * Check at compile time that something is of a particular type.
>  * Always evaluates to 1 so you may use it easily in comparisons.
>  */
>  #define typecheck(type,x) \
>  ({      type __dummy; \
>        typeof(x) __dummy2; \
>        (void)(&__dummy == &__dummy2); \
>        1; \
>  })
>
> #define typecheck_fn(type,function) \
> ({      typeof(type) __tmp = function; \
>       (void)__tmp; \
> })
>
> Can anyone help me, explain the above code typecheck. How does
> (void)(&__dummy == &__dummy2) evaluates to 1
>
> I appreciate any explain.

If dummy and dummy2 are of different types, then when you try and do a
pointer comparison (&dummy == &dummy2) it will produce a compiler
warning/error.

The actual comparison will always fail, but it doesn't matter since
the results aren't used.

typecheck always returns 1.

Dave Hylands

  parent reply	other threads:[~2011-01-31 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 17:03 Sri Ram Vemulpali
2011-01-31 17:20 ` Jamie Iles
2011-01-31 17:22 ` Geert Uytterhoeven
2011-01-31 17:44 ` Rajat Sharma
2011-01-31 18:03 ` Manish Katiyar
2011-01-31 20:23   ` Sri Ram Vemulpali
2011-01-31 20:26 ` Dave Hylands [this message]
2011-01-31 21:42   ` julie Sullivan

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=AANLkTimgTCdJfyKcyrpM-VgWtNCFonu2rvca+pkc+ebh@mail.gmail.com \
    --to=dhylands@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sri.ram.gmu06@gmail.com \
    --subject='Re: typecheck code' \
    /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

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).